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?
- 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.Cevap
- BDeploy 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.
- CDeploy 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.
- DDeploy 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.