Examkin

Question

Difficulty: Very hardDisaster Recovery and Business Continuity Execution

A healthcare enterprise is executing its disaster recovery strategy across Google Cloud regions us-central1 (primary) and us-east4 (secondary). The workload manages critical electronic health records and requires a strict Recovery Point Objective (RPO) of zero and a Recovery Time Objective (RTO) under 1 minute for database failover. Additionally, on-premises hybrid connectivity demands a sustained throughput of 15 Gbps for continuous data synchronization, and isolated spoke VPCs must route failover traffic through a central hub VPC to reach secondary regional services without establishing direct full-mesh peering between every spoke. Which combined Google Cloud architectural strategy meets all operational, performance, and disaster recovery execution requirements?

  1. Deploy Cloud Spanner using a multi-region instance configuration, provision Dedicated Interconnect for hybrid connectivity, and implement Network Connectivity Center with dynamic BGP routing for hub-and-spoke VPC architecture.Answer
  2. B
    Deploy Cloud SQL for PostgreSQL with cross-region asynchronous read replicas and automated promotion scripts, provision Dedicated Interconnect for hybrid connectivity, and implement Network Connectivity Center for hub-and-spoke VPC architecture.
  3. C
    Deploy Cloud Spanner using a multi-region instance configuration, establish aggregated HA VPN tunnels with Equal-Cost Multi-Path (ECMP) routing to reach 15 Gbps throughput, and implement Network Connectivity Center for hub-and-spoke VPC architecture.
  4. D
    Deploy Cloud Spanner using a multi-region instance configuration, provision Dedicated Interconnect for hybrid connectivity, and connect spoke VPCs directly to the central hub VPC using standard VPC Network Peering to route traffic transitively.

Answer

Deploying Cloud Spanner with multi-region synchronous replication satisfies the zero RPO and sub-minute RTO requirement. Dedicated Interconnect provides the required 15 Gbps hybrid bandwidth, and Network Connectivity Center enables non-transitive network routing limitations of standard VPC peering to be resolved.
The solution combining Cloud Spanner multi-region instance configuration, Dedicated Interconnect, and Network Connectivity Center satisfies all three explicit constraints: Cloud Spanner ensures RPO=0 via multi-region synchronous replication; Dedicated Interconnect reliably handles 15 Gbps hybrid traffic; and Network Connectivity Center enables managed hub-and-spoke routing without violating VPC peering transitivity boundaries.

Step-by-Step Solution

1
Evaluate data persistence requirements against RPO=0 and sub-minute RTO constraints.
Cloud SQL cross-region read replicas use asynchronous replication and manual/scripted promotion, which risks data loss (RPO > 0). Cloud Spanner multi-region configurations synchronously replicate writes across regions, ensuring RPO=0 and rapid automated failover.
Relational databases requiring absolute zero RPO across regions in GCP necessitate multi-region Cloud Spanner.
2
Assess hybrid network bandwidth requirements for 15 Gbps continuous sync.
HA VPN maxes out at 3 Gbps per tunnel (up to 5 Gbps in specific configurations) and requires complex multi-tunnel ECMP management for 15 Gbps. Dedicated Interconnect offers native 10 Gbps or 100 Gbps circuits suitable for high sustained throughput.
Dedicated Interconnect is the appropriate GCP pattern for sustained hybrid traffic above multi-gigabit thresholds.
3
Analyze hub-and-spoke VPC traffic routing constraints.
Standard VPC Network Peering is strictly non-transitive. Traffic cannot pass through a hub VPC to reach external or secondary regional destinations. Using Network Connectivity Center with Cloud Routers provides managed hub-and-spoke routing.
Transitive routing across spoke networks requires managed routing mechanisms such as Network Connectivity Center or VPN/Router appliance overlays.

Key Concept

Multi-region DR Execution with Cloud Spanner, Dedicated Interconnect, and Hub-and-Spoke Networking
Rate this question

Topics

Disaster Recovery and Business Continuity Execution

More questions from this topic