A line lists weights in both kg and lbs for the same item without a standard conversion. What is the problem?

A line lists weights in both kg and lbs for the same item without a standard conversion. What is the problem?

• A. Data formatting issue
• B. The weights are listed in both kilograms and pounds
• C. The measurements can be automatically converted
• D. Unit inconsistency without a standard conversion

Answer: (D)

This question tests unit consistency in data. When a single quantity is shown using more than one unit without a clear rule for converting between them, the data become inconsistent and unreliable for calculations or comparisons. In this line, weights appear in both kilograms and pounds for the same item, but there’s no standard conversion provided. That creates ambiguity: you don’t know which value to trust or how to combine them with other data, and automated calculations could be wrong if unit mismatches slip in. If a single unit were chosen (say, always kilograms) or if there were a clearly documented conversion factor and a consistent approach to store or convert values, the data would be usable. Listing both units isn’t inherently bad, but without a standard way to convert, the primary problem is the lack of a consistent, defined conversion. The other options describe surface aspects or remedies rather than the core issue. It isn’t primarily a formatting issue, since the layout isn’t the root cause. Simply having both units isn’t the problem in itself; the problem is that there’s no standard conversion to ensure those two representations align. And automatic conversion is a possible fix, not the problem itself.

This question tests unit consistency in data. When a single quantity is shown using more than one unit without a clear rule for converting between them, the data become inconsistent and unreliable for calculations or comparisons. In this line, weights appear in both kilograms and pounds for the same item, but there’s no standard conversion provided. That creates ambiguity: you don’t know which value to trust or how to combine them with other data, and automated calculations could be wrong if unit mismatches slip in.

If a single unit were chosen (say, always kilograms) or if there were a clearly documented conversion factor and a consistent approach to store or convert values, the data would be usable. Listing both units isn’t inherently bad, but without a standard way to convert, the primary problem is the lack of a consistent, defined conversion.

The other options describe surface aspects or remedies rather than the core issue. It isn’t primarily a formatting issue, since the layout isn’t the root cause. Simply having both units isn’t the problem in itself; the problem is that there’s no standard conversion to ensure those two representations align. And automatic conversion is a possible fix, not the problem itself.