A financial services organization is designing a high availability (HA) and disaster recovery (DR) strategy for a mission-critical database in Google Cloud. The system has the following requirements: High Availability (HA): Rapid, automatic failover with minimal disruption in the event of an unplanned data center or single-zone outage. Disaster Recovery (DR): Continuous protection and data redundancy across geographic locations to recover business operations if an entire Google Cloud region experiences a catastrophic failure. Which combination of primary and secondary storage location types should the organization implement?

Deploy a primary database instance with a synchronous standby replica in a secondary zone within the same region for HA, and configure an asynchronous replica in a secondary region for DR.: ### **What this solution is** This architecture combines **in-region zonal high availability** with **cross-region disaster recovery replication**. The primary database instance processes active read and write transactions while continuously replicating data to two separate locations: a standby instance in a secondary zone within the same primary region, and a read/standby replica located in an entirely different geographic secondary region. ### **How it meets the requirements** - **High Availability (HA) requirement (✓):** Deploying a standby replica in a secondary zone within the same region provides automated health monitoring and failover. If the primary zone suffers a localized hardware or power disruption, traffic seamlessly fails over to the secondary zone with minimal recovery time objective (RTO) and zero or near-zero recovery point objective (RPO). - **Disaster Recovery (DR) requirement (✓):** Replicating data asynchronously to a secondary region ensures geographic separation. If an entire region experiences a catastrophic natural disaster or wide-scale outage, the database in the secondary region can be promoted to become the new primary, ensuring business continuity. ### **Key advantages and capabilities** - **Multi-layered resilience:** Protects against both single-datacenter (zonal) incidents and broad geographic (regional) disruptions. - **Low operational latency:** Synchronous zonal replication maintains high performance for everyday transactions, while asynchronous cross-region replication prevents cross-continental network latency from slowing down write queries. - **Read scalability:** The secondary regional replica can often be leveraged for local read traffic or reporting queries during normal operational states. - **Managed automated failover:** Managed database services in Google Cloud automate the heartbeat detection and failover process between zones. ### **Why this is optimal** Combining **zonal replication for HA** with **regional replication for DR** directly aligns with enterprise best practices for mission-critical databases, matching maximum protection against localized faults without compromising transactional performance.