What does End-to-End Error indicate?

• A. Data corruption in the memory module
• B. Data corruption in the memory controller
• C. Data corruption in the controller path — serious
• D. Data corruption on the network path

Answer: (C)

End-to-end error means a data integrity issue that shows up as data moves from the source to the destination across the entire data path. The question points to the controller path as the problem area because the controller sits at the heart of how data flows through the system, coordinating inputs and outputs between memory, I/O, and other subsystems. A fault in this path can corrupt data across many transactions and across the full data path, making it a serious, system-wide end-to-end issue.

Local memory module corruption is typically isolated and often mitigated by ECC, so it doesn’t reflect an end-to-end fault through the controller. A fault in the memory controller is also problematic, but the phrasing here emphasizes the data path through the controller itself. Network path corruption would be an end-to-end issue too, but this item focuses on internal data flow, making the controller path the best match for an end-to-end error.