Question 300
At University astronomy project, the Google Cloud design for temporary sky-image processing is affected because large image batch runs only one weekend a month yet reserved VMs are always on. A review found that cost report shows accelerator nodes idle more than ninety percent of the time. The proposed response must account for the requirement that scientific jobs can checkpoint and resume after interruption. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
Explanation
Correct Answer
Assess preemption tolerance, GPU sizing and checkpoint intervals is the appropriate diagnostic because the observation—cost report shows accelerator nodes idle more than ninety percent of the time—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (large image batch runs only one weekend a month yet reserved VMs are always on) before the design is approved.
Incorrect Answers
The alternative “Test checkpoint restoration and quota-aware job retries before scaling” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Assess preemption tolerance, GPU sizing and checkpoint intervals” instead addresses the requested root-cause evidence.
The alternative “Use job orchestration with Spot VMs for interruptible batch computation” is target architecture selection; it does not establish why the observed path failed. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Assess preemption tolerance, GPU sizing and checkpoint intervals” instead addresses the requested root-cause evidence.
Preemptible nodes are unsuitable as unprotected authoritative state. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that scientific jobs can checkpoint and resume after interruption.


