During a disaster recovery test, the team discovers that the backup generator fails to start. What is the BEST immediate action?
Documenting allows the test to continue while capturing the failure for later analysis.
Why this answer
Option C is correct because the immediate priority during a disaster recovery test is to document the failure and continue the test to evaluate the remaining components of the DR plan. The backup generator failure is a specific issue that should be logged for post-test remediation, but aborting the test prematurely would lose valuable data on other failover mechanisms, such as UPS runtime, network redundancy, or application recovery. Proceeding with documentation ensures the test's integrity while capturing the incident for root cause analysis.
Exam trap
ISC2 often tests the misconception that any hardware failure during a DR test automatically invalidates the entire test, tempting candidates to choose 'Cancel the test' (Option B) instead of recognizing that documentation and continuation preserve the test's value for other critical components.
How to eliminate wrong answers
Option A is wrong because continuing the test with manual procedures bypasses the automated failover that the generator was supposed to support, invalidating the test's ability to measure true recovery time objectives (RTOs) and recovery point objectives (RPOs). Option B is wrong because canceling the test discards the opportunity to validate all other DR components (e.g., storage replication, DNS failover, load balancer health checks) that are independent of the generator; a partial test with documented issues is more valuable than no test. Option D is wrong because shutting down the data center is an extreme, unnecessary action that would cause a full outage, violating the principle of minimizing disruption during a test; the generator failure alone does not indicate an immediate safety or data loss risk.