hardMultiple ChoiceObjective-mapped
Cloud Digital Leader Practice Question: A solutions architect is designing a system that…
A solutions architect is designing a system that must remain available even if an entire Google Cloud region becomes unavailable due to a major disaster. Which deployment approach achieves this goal?
⚠ Common exam trap
Google Cloud often tests the distinction between zonal and regional fault tolerance, and the trap here is that candidates confuse multi-zone deployment (which handles zonal failures) with multi-region deployment (which is required for regional disaster recovery).
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Deploying the application across multiple Google Cloud regions so that if one region fails, other regions continue serving traffic
Deploying across multiple Google Cloud regions ensures that if an entire region becomes unavailable, traffic can be rerouted to healthy regions, achieving disaster recovery across regional failures. This approach leverages Google Cloud's global load balancing (e.g., External HTTPS Load Balancer with backend services in multiple regions) and regional managed instance groups to maintain availability even when a complete region is lost.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploying the application across multiple zones within the same Google Cloud region
Why it's wrong here
Multiple zones within a single Google Cloud region safeguard against localized failures such as hardware faults or zone-wide network issues, but they all share the region's physical and logical infrastructure. If the entire region becomes unavailable — due to a natural disaster, regional network partition, or infrastructure crisis — every zone in that region is impacted simultaneously. Regional multi-zonal deployments are a classic high-availability pattern but provide no disaster recovery protection. To survive a full regional outage, you must replicate workloads and data across geographically separate regions, not just across zones.
- ✗
Using a single zone but enabling automatic VM restart policies
Why it's wrong here
Automatic VM restart policies, such as those configured in a single-zone managed instance group, resume VMs on the same hardware or within the same zone when a failure is detected. However, if that zone or its hosting region experiences an outage, the restart service cannot schedule the VM anywhere else, because it has no capacity or placement target outside the failed zone. Additionally, auto-restart does not address data replication, load balancer failover, or network dependencies — so an application can still lose all traffic even if the VM reboots. This approach offers almost no protection against a zonal failure and zero protection against a regional disaster.
- ✓
Deploying the application across multiple Google Cloud regions so that if one region fails, other regions continue serving traffic
Why this is correct
Multi-region deployment is required to survive a full regional outage. By running active or active-passive instances in multiple distinct geographic regions, the system continues operating when any single region fails. Each region is geographically and infrastructure-independently isolated.
- ✗
Enabling Cloud Backup for all VMs in the deployment to allow rapid restoration after a regional failure
Why it's wrong here
Cloud Backup provides point-in-time snapshots for data restoration, but it does not create a fully provisioned, ready-to-serve infrastructure. In a regional outage, you must first restore the backup in a new region, rebuild or reattach VMs, and reconfigure networking — a process with a significant recovery time objective (RTO). During that restoration window, user traffic cannot be served, so the system is not continuously available. Thus, backup is a data-protection mechanism, not a high-availability strategy, and cannot match the near-zero downtime of a multi-region deployment.
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Region
A region is a distinct geographic location where a cloud provider operates multiple data centers that are connected by low-latency networks and provide cloud services.
Key term
Recovery
Recovery is the process of restoring systems, data, and operations after a security incident, failure, or disaster to return to normal functioning.
About these practice questions
Courseiva writes every GCDL question from scratch — 829 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.