220-1101 Question 353
Single answerTest developmentA technician is validating a newly built desktop before it is deployed to a graphic design department. The user reports that during long rendering jobs, the system suddenly reboots, but short office tasks run normally. The technician has already confirmed the OS is fully updated and the power outlet is working correctly. Which action should the technician take NEXT to best isolate the cause?
- A
Run a CPU and GPU stress test while monitoring system temperatures and power stability
- B
Replace the keyboard and mouse to rule out peripheral compatibility issues
- C
Reinstall the operating system to eliminate possible application corruption
- D
Disable automatic updates so background processes do not interrupt rendering jobs
Show answer and explanation
Correct answer: A
Explanation
This question focuses on test development in a real A+ Core 1 context: building an appropriate diagnostic test based on the reported symptom. Since the failure happens only under sustained heavy workload, the technician should develop a targeted test that reproduces the condition safely and consistently. Stress testing the CPU and GPU while monitoring temperatures, fan operation, and power behavior is a practical way to isolate overheating, insufficient cooling, or PSU instability. CompTIA troubleshooting best practices emphasize identifying the problem, establishing a theory, and testing the theory with the least invasive and most relevant method before making major changes. Manufacturer hardware diagnostics, BIOS/UEFI hardware monitoring, and reputable stress-testing utilities are commonly used for this purpose.
- A. Correct.
Correct. Because the reboots occur only during long, high-load rendering jobs, the most appropriate next step is targeted test development: reproduce the failure under controlled conditions using a CPU/GPU stress test while monitoring thermal and power behavior. This helps isolate whether overheating, an inadequate PSU, unstable cooling, or component failure is the root cause. In A+ troubleshooting, technicians should test the suspected subsystem based on the symptom pattern rather than make broad changes first.
- B. Incorrect.
Incorrect. Input peripherals are unlikely to cause sudden reboots that occur specifically under sustained rendering loads. This option reflects a poor test plan because it does not align the test with the observed symptom. A+ troubleshooting emphasizes developing tests that are relevant to the probable cause.
- C. Incorrect.
Incorrect. Reinstalling the OS is too invasive and premature at this stage. The issue appears workload-dependent and is more consistent with hardware stress, thermal shutdown, or power instability than general software corruption. A technician should first create a repeatable test to confirm whether the failure happens under load before performing disruptive remediation.
- D. Incorrect.
Incorrect. Automatic updates are not the best explanation for crashes that happen during long rendering tasks but not during light use. Disabling updates does not meaningfully test the suspected cause and may reduce system security. This distractor represents the common mistake of changing settings without first collecting evidence through controlled testing.