Examkin

Soru

Zorluk: ZorDisaster Recovery and Business Continuity Execution

A global financial service platform hosts a mission-critical payment processing engine spanning Google Cloud `us-central1` (primary) and `us-east4` (secondary). The architecture connects to an on-premises mainframe transferring up to 15 Gbps of state data. Business requirements mandate a Recovery Point Objective (RPO) of under 1 minute and a Recovery Time Objective (RTO) of under 15 minutes during a total regional failover. Compute workloads run on Compute Engine Managed Instance Groups (MIGs), and relational data uses Cloud SQL for PostgreSQL with a cross-region read replica in `us-east4`. During a catastrophic regional outage in `us-central1`, which disaster recovery failover procedure should the cloud architecture team execute to ensure operational continuity within compliance bounds?

  1. Promote the cross-region Cloud SQL read replica in `us-east4` to standalone primary, redirect on-premises hybrid traffic through pre-provisioned Dedicated Interconnect VLAN attachments in `us-east4`, and scale the secondary region MIGs to handle production load via Cloud Load Balancing.Cevap
  2. B
    Provision a high-availability HA VPN gateway with multiple active 3 Gbps IPsec tunnels in `us-east4` to route hybrid traffic, promote the Cloud SQL replica in `us-east4`, and update Cloud DNS records to point to the secondary compute endpoints.
  3. C
    Promote the Cloud SQL replica in `us-east4`, and route secondary region compute traffic to the on-premises environment by transitively passing packets from the `us-east4` application VPC through an existing VPC Network Peering connection into the `us-central1` hybrid transit VPC.
  4. D
    Initiate automated Cloud Storage snapshot restoration of the primary database in `us-east4`, submit an immediate request for Compute Engine CPU core quota increases in `us-east4`, and re-route traffic using global Cloud Load Balancing.

Cevap

Promote the cross-region Cloud SQL read replica in us-east4 to standalone primary, redirect on-premises hybrid traffic through pre-provisioned Dedicated Interconnect VLAN attachments in us-east4, and scale the secondary region MIGs to handle production load via Cloud Load Balancing.
Executing failover by promoting a cross-region read replica satisfies sub-minute RPO, pre-provisioned Dedicated Interconnect VLAN attachments in the secondary region sustain 15 Gbps hybrid traffic without tunnel throughput limits, and warm-standby MIG scaling ensures recovery well within the 15-minute RTO envelope.

Adım Adım Çözüm

1
Analyze RPO, RTO, and bandwidth requirements.
RPO < 1 min, RTO < 15 min, Bandwidth = 15 Gbps between GCP and on-premises.
Bandwidth demands above 10 Gbps mandate Dedicated Interconnect rather than HA VPN. Sub-minute RPO requires asynchronous database replication rather than cold backup/snapshot restoration.
2
Evaluate network routing constraints.
Transitive routing over VPC Peering is unsupported.
VPC Network Peering cannot pass traffic transitively to an on-premises interconnect located in another peered VPC.
3
Select the compliant failover procedure.
Promote cross-region replica, leverage secondary pre-provisioned Dedicated Interconnect, and scale secondary MIGs.
Meets all operational SLAs, hybrid throughput limits, and GCP network architecture rules.

Anahtar Kavram

Disaster Recovery Execution and Hybrid Network Routing under Strict RPO/RTO
Bu soruyu puanla

Konular

Disaster Recovery and Business Continuity Execution

Bu konudan daha fazla soru