Difficulty: Easy
Correct Answer: Incorrect
Explanation:
Introduction / Context: Hexadecimal (base 16) and Binary-Coded Decimal (BCD) both use 4-bit groups, which often leads to confusion. However, they encode different domains: hex digits represent values 0–15, while standard BCD encodes decimal digits 0–9 only. This question probes whether you can separate these encodings conceptually and practically.Given Data / Assumptions:
Concept / Approach: Although both use nibbles, BCD is not “encoded by hex.” BCD stores each decimal digit separately in 4 bits to preserve decimal semantics (e.g., 39 decimal → BCD 0011 1001). Hexadecimal is a base-16 numeral system; 0x27 equals decimal 39 but as a single base-16 number, not two decimal digits encoded. Treating hex and BCD as interchangeable causes value misinterpretations in registers and memory maps.Step-by-Step Solution:
Represent 59 decimal in BCD: 0101 1001 (two nibbles).Represent 59 decimal in hex: 0x3B (0011 1011), a different bit pattern.Observe that BCD preserves decimal digits; hex represents a base-16 magnitude.Verification / Alternative check:
Round-trip conversions confirm that hex and BCD agree numerically only after proper base interpretation, not by raw bit equality.Why Other Options Are Wrong:
Correct: Would imply hex is the encoding mechanism for BCD, which is false.True only for values 0–9: While the hex symbols 0–9 exist, hex continues with A–F; BCD forbids A–F codes.Depends on signed magnitude: Sign representation is orthogonal to the radix/encoding distinction.Common Pitfalls:
Reading a BCD byte as hex and getting the wrong decimal value.Using A–F nibbles in BCD fields, which are invalid.Final Answer:
Incorrect
Discussion & Comments