Examkin

Soru

Zorluk: OrtaDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A global smart grid utility provider hosts its real-time telemetry processing platform on Google Cloud. The primary production environment runs in us-central1, with us-east4 designated as the disaster recovery (DR) region. The enterprise requires a non-disruptive, periodic DR validation exercise to verify that Recovery Point Objective (RPO < 15 minutes) and Recovery Time Objective (RTO < 1 hour) are met. In what correct sequential order should the Cloud Architect execute the DR validation procedure?

  1. 1Verify regional resource quotas in the DR region (us-east4) and submit quota increase requests if required limits are not met.
  2. 2Provision Compute Engine capacity reservations in us-east4 to guarantee compute resource availability for failover instances.
  3. 3Create an isolated testing VPC in us-east4 and promote read-only database replicas or mount point-in-time snapshots in isolation.
  4. 4Execute synthetic workload smoke tests in the isolated DR environment to validate data consistency, ingestion rates, and RPO/RTO metrics.
  5. 5Tear down temporary test infrastructure, release test capacity reservations, and document validation metrics for compliance reporting.

Cevap

The correct procedural order is: (1) Verify regional resource quotas in us-east4, (2) Provision Compute Engine capacity reservations in us-east4, (3) Create an isolated testing VPC and promote read-only database replicas, (4) Execute synthetic workload smoke tests to validate RPO and RTO metrics, and (5) Tear down test infrastructure and document validation metrics.
A structured disaster recovery validation procedure must follow a strict dependency order. First, cloud quota prerequisites must be verified and adjusted because quota increases require administrative processing time. Second, capacity reservations must be created in the target region to guarantee that hardware is available. Third, an isolated environment (VPC and database snapshots/replicas) must be established so that testing does not impact live operations. Fourth, synthetic tests are run within the sandbox to measure RPO/RTO against target objectives. Finally, test infrastructure is dismantled to prevent unnecessary spend, and audit logs are archived.

Adım Adım Çözüm

1
Audit and request regional quota increases in the target DR region.
Ensures the project has sufficient quota headroom for compute, networking, and storage resources.
Quota adjustments may take time to process; attempting to provision resources without sufficient quota will fail.
2
Acquire Compute Engine capacity reservations in the DR region.
Guarantees compute capacity is reserved in target zones regardless of regional demand.
Without reservations, resource availability cannot be guaranteed during regional outages or large-scale DR drills.
3
Set up an isolated sandbox network and populate it with test data replicas/snapshots.
Creates a safe environment mirroring production state up to the target RPO.
Isolation prevents test traffic or data writes from corrupting primary production systems.
4
Run validation tests and measure RTO/RPO metrics.
Empirically verifies that failover automation meets recovery requirements.
Provides actual metrics on startup duration, database sync integrity, and service availability.
5
Decommission test resources and log exercise evidence.
Optimizes costs by removing temporary infrastructure and satisfies enterprise compliance requirements.
Temporary test resources should be cleaned up immediately following test completion.

Anahtar Kavram

Disaster Recovery Validation Sequence and Non-Disruptive Testing Procedures
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation