Soru

Zorluk: KolayDisaster Recovery and Business Continuity Execution

During a major regional outage in Google Cloud, your operations team must execute a manual disaster recovery runbook to fail over a web application and its database from the primary region to a secondary standby region. In what order should you perform the following disaster recovery execution steps?

  1. 1Promote the cross-region database read replica in the secondary region to function as a standalone primary database.
  2. 2Update secondary region application workloads with the connection endpoints of the newly promoted standalone database.
  3. 3Update Cloud DNS routing policies to switch incoming user traffic from the primary region endpoint to the secondary region load balancer.
  4. 4Verify application functionality and operational telemetry metrics in the secondary region to confirm successful failover.

Cevap

The correct operational sequence is: first, promote the cross-region database read replica to standalone primary status; second, update secondary application workload connections to point to the new database; third, update Cloud DNS routing policies to direct user traffic to the secondary region; and fourth, verify application telemetry and functionality.
Executing disaster recovery requires ensuring data tier readiness prior to application connection updates and traffic redirection. Promoting the cross-region database replica ensures a writable database exists. Reconfiguring the secondary application instances allows them to communicate with the database. Updating Cloud DNS shifts user traffic safely to the secondary region. Finally, operational telemetry verification ensures business continuity success.

Adım Adım Çözüm

1
Promote Database Replica
Database in the secondary region becomes writable.
Data persistence layer readiness is required before application instances can execute stateful operations.
2
Reconfigure Secondary Application Workloads
Secondary application instances target the new writable database endpoint.
Prevents database connection failures when incoming requests start arriving.
3
Reroute External Network Traffic via Cloud DNS
User requests are directed to the secondary region's load balancer.
Traffic should only be introduced once backend infrastructure is fully reconfigured and ready.
4
Perform System Validation and Telemetry Checks
Confirmed disaster recovery failover completion and operational stability.
Validates that business continuity objectives have been met under live operational conditions.

Anahtar Kavram

Disaster Recovery Failover Execution Sequence
Tahmini Süre:1m 0s
Bu soruyu puanla