Examkin

Soru

Zorluk: OrtaDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A healthcare provider hosts a critical telemedicine application on Google Cloud using a multi-region deployment across us-central1 (primary) and us-east4 (secondary). The backend relies on Cloud Spanner for transactional patient records and Compute Engine Managed Instance Groups (MIGs) for application servers behind a Global External Application Load Balancer. The business continuity requirement specifies a Recovery Point Objective (RPO) of zero and a Recovery Time Objective (RTO) under 15 minutes. Which validation procedure should the cloud architect implement to periodically verify DR readiness in us-east4 without interrupting live production traffic in us-central1?

  1. Pre-verify regional compute quotas in us-east4, monitor Cloud Spanner replication latency metrics, and conduct synthetic health checks against isolated test endpoints provisioned on the us-east4 MIG via Cloud DNS weighted routing.Cevap
  2. B
    Initiate an immediate full failover drill during peak hours by updating global load balancer backends to us-east4, submitting Compute Engine quota increase requests if instance allocation errors are observed during the test.
  3. C
    Export daily Cloud Spanner backups to Cloud Storage, restore them into a Cloud SQL instance in us-east4 during validation drills, and spin up a cold-standby MIG to evaluate system recovery speed.
  4. D
    Establish an HA VPN tunnel between us-central1 and us-east4 to stream VM memory states across regions, and validate failover by executing a forced power-off on primary VM instances.

Cevap

Pre-verify regional compute quotas in us-east4, monitor Cloud Spanner replication latency metrics, and conduct synthetic health checks against isolated test endpoints provisioned on the us-east4 MIG via Cloud DNS weighted routing.
The procedure that pre-verifies regional quotas, monitors Spanner replication metrics, and executes synthetic testing via isolated routing paths validates DR readiness across compute, storage, and networking layers without causing operational disruption to live users.

Adım Adım Çözüm

1
Analyze RPO and RTO validation requirements
Zero RPO requires continuous multi-region synchronous/near-synchronous replication (provided natively by Cloud Spanner), while RTO under 15 minutes requires pre-allocated or rapidly scalable infrastructure in the secondary region.
DR validation procedures must verify that data replication lag remains near zero and that secondary infrastructure can immediately absorb production load.
2
Evaluate prerequisite environment validation checks
Regional resource quotas (e.g., Compute Engine vCPUs, in-use IP addresses) in us-east4 must be verified in advance to avoid capacity throttling during failover.
Quota increases in Google Cloud require administrative processing time and cannot be requested reactively during a DR event or time-bounded drill.
3
Design a non-disruptive traffic validation mechanism
Use Cloud DNS weighted routing or isolated test URLs to route synthetic test transactions to the secondary MIG while primary production traffic continues uninterrupted.
Validating DR capabilities should confirm full stack health in the secondary region without impacting live user sessions.

Anahtar Kavram

Disaster Recovery Validation & Quota Governance
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation