Question 550
During a high-traffic model-service launch at an online commerce company, engineers report the following issue: Operators cannot see power supply alarms because they only query Linux system logs. The affected work supports product search, recommendations and fraud screening; peak request demand makes degraded predictions visible to customers. Choose TWO: one corrective approach and one result demonstrating it works. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Use a secured baseboard management controller and out-of-band path to inspect system sensors, power and remote console status independently of the host operating system. This fits the specific reported issue: Operators cannot see power supply alarms because they only query Linux system logs. The corresponding failure being reduced is: Relying only on the workload OS for management can prevent diagnosis or recovery when a node crashes or its production network fails.
Correct independent evidence. An authorized operator retrieves board-level health and remote console information over the protected management network while the host OS is unavailable. This verifies the corrective approach for the affected product search, recommendations and fraud screening instead of treating an architecture diagram alone as success.
Incorrect Answers
Not the most direct the action-and-evidence pair for these facts. Maintain an inventory of GPU systems, drivers, firmware, network devices and approved configuration versions with controlled rollout and reconciliation. This choice concerns cluster inventory firmware and configuration baseline and may be valid in another design. But this case reports 'Operators cannot see power supply alarms because they only query Linux system logs', which calls for reasoning about bmc and out-of-band server health administration. The targeted response is: Use a secured baseboard management controller and out-of-band path to inspect system sensors, power and remote console status independently of the host operating system.
Not the most direct the action-and-evidence pair for these facts. Correlate supported GPU error counters and Xid or ECC events with driver logs, diagnostics and affected workloads before deciding on remediation or hardware replacement. This choice concerns gpu reliability events and diagnostic triage and may be valid in another design. But this case reports 'Operators cannot see power supply alarms because they only query Linux system logs', which calls for reasoning about bmc and out-of-band server health administration. The targeted response is: Use a secured baseboard management controller and out-of-band path to inspect system sensors, power and remote console status independently of the host operating system.
Not the most direct the action-and-evidence pair for these facts. Several representative users submit jobs and the scheduler allocates only authorized GPU resources under the published priority and quota policy. This choice concerns slurm batch queues fair-share and reservations and may be valid in another design. But this case reports 'Operators cannot see power supply alarms because they only query Linux system logs', which calls for reasoning about bmc and out-of-band server health administration. The targeted response is: Use a secured baseboard management controller and out-of-band path to inspect system sensors, power and remote console status independently of the host operating system.