Difficulty: Easy
Correct Answer: Correct
Explanation:
Introduction / Context:
Interpreting hex byte sequences as ASCII characters is a common task when reading protocol traces, memory dumps, or file headers. This question checks the learner’s ability to map each hex byte to its ASCII character and recognize the resulting string.
Given Data / Assumptions:
Concept / Approach:
Decode each byte: 0x53→‘S’, 0x54→‘T’, 0x55→‘U’, 0x44→‘D’, 0x45→‘E’, 0x4E→‘N’, 0x54→‘T’. Concatenate to form the string. No endianness issues arise for byte-wise character sequences; endianness affects multi-byte numeric fields, not the order of bytes already presented in a stream.
Step-by-Step Solution:
Verification / Alternative check:
Consult any ASCII table: hexadecimal column for uppercase letters confirms the mappings. Many hex editors display an ASCII panel that would show “STUDENT” for these bytes.
Why Other Options Are Wrong:
Common Pitfalls:
Reading hex without verifying with a table; confusing case (0x53 is uppercase S, not lowercase s which is 0x73); assuming CPU endianness changes pre-ordered byte streams.
Final Answer:
Correct
Discussion & Comments