Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Zonal High Availability with Cross-Region Disaster Recovery
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,132 more like it. Try 10 free: instant score, no account.
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?
Explanations
Deploy a primary database instance in a single zone and configure scheduled daily backups stored exclusively within that same primary zone.
Deploy a primary database instance in a single zone and configure scheduled daily backups stored exclusively within that same primary zone.
What this option is/does
This configuration represents a single-zone, standard availability deployment where the active database instance and its storage snapshots or backups reside within a single availability zone inside a single region.
Why it doesn't meet the requirement
- Fails HA requirements (✗): There is no standby instance or automated failover mechanism. If the specific zone encounters a power failure or network partition, the database becomes completely unavailable until that zone recovers.
- Fails DR requirements (✗): Because both the live instance and backups are confined to the same zone and region, a regional disaster or localized storage failure could destroy both the operational database and its backups simultaneously.
Key characteristics and limitations
- Single point of failure: Entire database uptime depends strictly on the stability of a single data center.
- Manual recovery: Recovery requires provisioning a new instance and restoring from backup, which takes significant time (high RTO) and loses data created since the last backup (high RPO).
- No geographic redundancy: No copies of the data exist outside the primary zone.
This answer would be correct if
The workload were a non-critical development or testing environment where downtime is acceptable and the primary goal is minimizing infrastructure costs rather than providing high availability and disaster recovery.
Deploy a primary database instance in a single zone and rely solely on nightly exports to a secondary region without zonal standby redundancy in the primary region.
Deploy a primary database instance in a single zone and rely solely on nightly exports to a secondary region without zonal standby redundancy in the primary region.
What this option is/does
This approach uses a single-zone primary database paired with scheduled batch exports copied over to an external secondary region on a 24-hour cycle.
Why it doesn't meet the requirement
- Fails HA requirements (✗): Without a synchronous standby replica in a secondary zone, any outage in the primary zone causes immediate downtime with no automated failover.
- Fails modern DR requirements (✗): Nightly exports result in a Recovery Point Objective (RPO) of up to 24 hours, meaning an entire day's worth of financial transactions could be permanently lost if the primary region fails before the next scheduled export.
Key characteristics and limitations
- High RTO and RPO: Restoring a database from a nightly export dump in a secondary region is a slow, manual process resulting in extended downtime and major data loss.
- No continuous replication: Transactions occurring between export intervals are not protected against region-level failures.
- Lacks automated failover: System administrators must manually provision and configure replacement infrastructure during an outage.
This answer would be correct if
The workload consisted of batch analytical datasets or non-transactional archives where up to 24 hours of data loss and hours of restoration time are fully acceptable within business SLAs.
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.
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.
Zonal HA with Cross-Region DR
System Architecture
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.
Deploy a primary database instance with multiple read replicas distributed across zones in a single region, without configuring any cross-region replication.
Deploy a primary database instance with multiple read replicas distributed across zones in a single region, without configuring any cross-region replication.
What this option is/does
This configuration implements multi-zone read scaling and local high availability within a single Google Cloud region, where read replicas offload read-heavy traffic across different zones.
Why it doesn't meet the requirement
- Partially meets HA (✓): Distributing read replicas across multiple zones improves read resiliency and provides local failover candidates within that specific region.
- Fails DR requirements (✗): Because all instances and storage locations remain inside one region, the deployment lacks geographic disaster recovery. A major regional disruption, fiber cut, or regional service outage would render all replicas unavailable at the same time.
Key characteristics and limitations
- Intra-region containment: Data redundancy is strictly confined to the boundaries of a single metropolitan region.
- Zero cross-region protection: No secondary geographic location is available to take over production traffic during a regional disaster.
- Primary focus on read scalability: Read replicas primarily enhance query throughput rather than comprehensive regional disaster recovery.
This answer would be correct if
The business requirements only specified protection against localized single-zone hardware failures and read scaling within a single geographic region, without demanding disaster recovery protection against regional outages.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 1,132 practice questions across all 4 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAssociate Data Practitioner
Cloud Storage Dual-Region
Distinguish between primary and secondary data storage location type (e.g., regions, dual-regions, multi-regions, zones) for data redundancy
FundamentalAssociate Data Practitioner
Cloud Storage Dual-Region
Distinguish between primary and secondary data storage location type (e.g., regions, dual-regions, multi-regions, zones) for data redundancy
FundamentalAssociate Data Practitioner
Transfer Appliance vs Storage Transfer Service
Choose the appropriate data transfer tool (e.g., Storage Transfer Service, Transfer Appliance)
FundamentalAssociate Data Practitioner
Uniform Bucket-Level Access
Compare methods of access control for Cloud Storage (e.g., public or private access, uniform access)
FundamentalAssociate Data Practitioner
Cloud Storage Predefined Roles
Differentiate between basic roles, predefined roles, and permissions for data services (e.g., BigQuery, Cloud Storage)
IntermediateProfessional Cloud Architect
Spot VM Preemption Graceful Shutdown
Compute volatility configuration (spot vs. standard)
Last updated