Q: 3
Which file is a sequence of bytes organized into blocks understandable by the system’s linker?
Options
Discussion
Yeah, not A. The linker processes object files, not executables. Option C is correct here since object files contain the necessary blocks and symbol info. Executable (A) is a common trap because it sounds like the final product. Pretty sure C is right but let me know if there's another view.
Its C, since object files (.obj or .o) are what the linker actually reads and merges. Source files go to the compiler first, not straight to the linker. Seen this in practice labs too, but open to correction if I missed something.
It’s C. The linker takes object files as input, not executables or source files. Object files have the right format-organized in sections like .text, .data that the linker understands. Wouldn’t bet on any other option here.
Can EC-Council not write a less confusing question for once? C
C That’s what the linker actually uses, executables come after. Pretty sure this is it, unless there’s some weird wording here.
Pretty sure it's C, not A. Executable is tempting but linker uses object files.
A is wrong, C. Had something like this in a mock and object file was the answer.
C
A or C, tough one. I thought executables (A) are also arranged in block sections and the linker definitely deals with them when creating final output. But if they're asking what the linker "understands" as input, maybe C is more correct. Still feels like A could be close. Open to other thoughts on why it wouldn't be A.
B
Be respectful. No spam.