Examkin

Question

Difficulty: EasyDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An organization is executing a planned disaster recovery (DR) validation drill for a mission-critical web application on Google Cloud. Arrange the following steps into the correct sequence from first to last to ensure a successful failover test.

  1. 1Verify resource quota limits and capacity availability in the target disaster recovery region.
  2. 2Verify database replication catch-up and confirm that the Recovery Point Objective (RPO) target is met.
  3. 3Promote the secondary database replica to primary status and scale up standby compute workloads.
  4. 4Update Cloud DNS records and global Cloud Load Balancing routing to direct client traffic to the secondary region.

Answer

The correct chronological sequence for DR validation is: (1) Verify resource quota limits and capacity availability in the target disaster recovery region, (2) Verify database replication catch-up and confirm that the Recovery Point Objective (RPO) target is met, (3) Promote the secondary database replica to primary status and scale up standby compute workloads, and (4) Update Cloud DNS records and global Cloud Load Balancing routing to direct client traffic to the secondary region.
A structured DR validation procedure progresses systematically: verifying environmental capacity (quotas), confirming data state and RPO compliance, promoting infrastructure and databases, and finally updating network routing to shift user traffic.

Step-by-Step Solution

1
Perform regional quota and capacity pre-checks.
Ensures that target Compute Engine and network quotas in the DR region are sufficient for failover.
Failing to check quota availability first can cause failover operations to fail mid-execution.
2
Check replication state and validate RPO compliance.
Confirms data catch-up state between primary and standby database instances.
Promoting a standby database before verifying replication status can cause data loss exceeding RPO limits.
3
Promote database and activate application instances.
Establishes a fully operational primary data layer and application pool in the secondary region.
Backend services must be online and healthy before accepting user requests.
4
Switch DNS and load balancer traffic routing.
User traffic is seamlessly redirected to the newly promoted secondary environment.
Routing traffic prior to infrastructure readiness results in failed user connections and outage errors.

Key Concept

Disaster Recovery Validation Procedure Sequence
Rate this question

Topics

Developing Procedures for Business Continuity and Disaster Recovery Validation