Examkin

Soru

Zorluk: Çok zorDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An enterprise freight logistics company hosts its core real-time container tracking application on Google Cloud. The primary workload operates out of `us-central1`, with a secondary disaster recovery (DR) environment prepared in `us-east4` to satisfy a recovery point objective (RPO) of near-zero and a recovery time objective (RTO) of 15 minutes. The architecture team is designing an automated validation procedure for an upcoming unannounced DR simulation drill. The objective is to validate full regional failover capabilities, end-to-end network path integrity, and database readiness while minimizing risk to live production operations. Which TWO operational procedures must be incorporated into the DR validation framework to achieve this goal? (Select TWO.)

  1. Programmatically verify and reserve required Compute Engine capacity and regional quota limits in us-east4 prior to executing the failover drill.Cevap
  2. Inject synthetic transactions carrying dedicated test headers into the us-east4 failover endpoint to validate data ingestion and routing prior to updating production DNS records.Cevap
  3. C
    Reconfigure the primary transactional database to switch from continuous synchronous replication to daily snapshot restoration in us-east4 during the test window to prevent data corruption.
  4. D
    Re-route all test validation traffic from Dedicated Interconnect over temporary HA VPN tunnels to ensure complete physical separation between production and test network paths.

Cevap

The validation framework must include programmatically verifying and reserving regional Compute Engine quotas and capacity in the DR region prior to execution, as well as injecting synthetic test transactions into the failover endpoint to validate data ingestion and network routing before modifying production DNS entries.
A robust DR validation procedure requires pre-verifying regional resource quotas and capacity reservations in the failover region to avoid provisioning delays during failover. Additionally, injecting synthetic transactions into the DR environment validates complete application and network functionality prior to updating production DNS records.

Adım Adım Çözüm

1
Evaluate compute resource readiness and quota limits in the target disaster recovery region.
Ensure that the DR region (us-east4) has active capacity reservations and adequate API quota limits to instantiate required compute instances dynamically during failover.
Failing to pre-check regional quotas and capacity reservations can cause infrastructure provisioning failures during DR execution under load.
2
Establish synthetic testing mechanisms for traffic and data path verification.
Execute end-to-end transaction validation against the failover regional endpoint using synthetic telemetry tagged with test headers.
Synthetic validation confirms operational readiness of network routes, application services, and database writes in the failover region without impacting live production user sessions.

Anahtar Kavram

Developing Procedures for Business Continuity and Disaster Recovery Validation
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation