Study guide

5.2 Regional Resource Placement & High Availability Planning

Google Cloud Associate Cloud Engineer ACE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan

2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups

3 Chapter 3: APIs, Quotas & Billing Configuration

3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts

4 Chapter 4: Planning Compute & Storage Resources

4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types

5 Chapter 5: Planning Network Resources

5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard

6 Chapter 6: Deploying Compute Engine Workloads

6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration

7 Chapter 7: Deploying Google Kubernetes Engine Workloads

7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE

8 Chapter 8: Deploying Serverless & Event-Driven Applications

8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc

9 Chapter 9: Deploying Data Solutions

9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud

10 Chapter 10: Deploying Networking Resources & Infrastructure as Code

10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm

11 Chapter 11: Managing Compute Engine & GKE in Production

11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE

12 Chapter 12: Managing Cloud Run, Storage & Database Operations

12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)

13 Chapter 13: Networking Operations, Monitoring & Logging

13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

14 Chapter 14: IAM Policies & Role Types

14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles

15 Chapter 15: Service Accounts & Security Configuration

15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials

16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy

16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist

5.2 Regional Resource Placement & High Availability Planning

Key Takeaways Explain This Topic AI

Google Cloud runs 43 regions and 130 zones worldwide (mid-2026); zones within a region are linked by low-latency connections that enable synchronous cross-zone replication.

Zonal resources have no built-in failure protection; regional resources spanning 2+ zones survive a single zone outage; multi-regional resources survive a full region outage.

Compute Engine's SLA is 99.5% for a single-zone instance versus 99.99% for a Regional Managed Instance Group spanning multiple zones.

A Regional Persistent Disk must be explicitly provisioned with cross-zone replication — attaching a zonal disk to instances in two zones does not create redundancy.

Region selection should weigh latency, data residency/compliance, service availability, pricing, and disaster recovery posture, not just proximity to users.

Last updated: July 2026

Why Regional Placement Planning Matters

Domain 2 of the ACE exam guide asks candidates to plan "availability of resource locations" — in plain terms, deciding whether a workload should live in one zone, span multiple zones in a region, or spread across multiple regions. This decision drives both the availability SLA a workload can achieve and its cost and latency profile, and it shows up constantly in ACE scenario questions framed as "the application must survive a zone outage" or "must survive a regional outage."

Regions and Zones: The Physical Model

Google Cloud's infrastructure is organized into regions (independent geographic areas, such as us-central1 or europe-west1 ) and zones (isolated deployment areas within a region, such as us-central1-a , each mapping to distinct physical infrastructure with its own power, cooling, and networking). As of mid-2026, Google Cloud operates 43 regions and 130 zones worldwide, and most regions contain three or more zones spread across three or more physical data centers (a handful of newer regions — Stockholm, Mexico, Osaka, and Montreal — currently run three zones across only one or two physical buildings). Zones within a region are connected by high-bandwidth, low-latency links, which is what makes cross-zone replication practical for both compute and storage.

Zonal vs. Regional vs. Multi-Regional Resources

Placement Example resources Failure domain covered Typical SLA behavior

Zonal Single Compute Engine VM, zonal Persistent Disk, zonal GKE cluster None beyond the single zone Lowest — a zone outage takes the resource down

Regional Regional Managed Instance Group (2+ zones), Regional Persistent Disk, regional GKE cluster, Cloud SQL with HA Any single zone in the region Higher — designed to survive one zone failure

Multi-regional Multi-region Cloud Storage bucket, multi-region Spanner instance, multi-region BigQuery dataset An entire region Highest — designed to survive a full region outage

A zonal resource is the cheapest and simplest, but a zone-level incident (power loss, network partition, a bad rollout) takes it offline with no automatic recovery. A regional resource — most importantly a Regional Managed Instance Group spanning two or more zones, or a Regional Persistent Disk , which synchronously replicates data across two zones in the same region — keeps running if any single zone in that region fails, because healthy capacity in the surviving zone(s) absorbs the load. A multi-regional resource goes a step further, replicating across geographically separate regions so an entire region can be lost without an outage — the pattern used for global Cloud Storage buckets and multi-region Spanner configurations.

SLA Numbers Worth Memorizing

Compute Engine's published Service Level Agreement draws a clear line between these placement choices: a single-zone instance is covered at 99.5% monthly uptime (assuming SSD or Balanced Persistent Disk), while an instance workload running as a Regional Managed Instance Group across two or more zones is covered at 99.99% monthly uptime. That's the difference between roughly 3.6 hours of allowed downtime per month and about 4.4 minutes — a gap large enough that "which SLA tier does this architecture qualify for" is a recurring ACE exam pattern. The same logic extends to Cloud SQL: enabling High Availability (HA) configuration creates a standby instance in a second zone with synchronous replication and automatic failover, moving a database from a single point of failure to a design that survives a zone outage.

Choosing a Region: Beyond "Closest to My Users"

Region selection is a planning decision, not just a technical one. Candidates should weigh:

Latency — placing compute close to end users or to a dependent on-premises system minimizes round-trip time.

Compliance and data residency — some workloads (regulated financial or health data, government contracts) must stay within a specific country or economic region.

Service and SKU availability — not every Google Cloud product or machine type is available in every region; newer regions sometimes lag on GPU/TPU SKUs or specific managed services.

Pricing — compute, storage, and especially egress pricing vary by region; multi-region architectures should account for the cost of cross-region replication traffic, not just the storage itself.

Disaster recovery posture — an active-passive design (standby resources in a second region, activated on failover) costs less to run but recovers more slowly than active-active (traffic already split across two regions), which costs more but has near-zero recovery time.

Exam Scenarios

Scenario 1: A retail company's checkout service must stay available if a single Google Cloud zone experiences an outage, but a full regional outage is an acceptable (rare) risk given the budget. Answer: Deploy a Regional Managed Instance Group across at least two zones in one region, backed by a Regional Persistent Disk or a stateless design — this meets the 99.99% SLA tier without paying for full multi-region redundancy.

Scenario 2: A hospital network's patient records database cannot go offline even if an entire Google Cloud region fails, and it must remain queryable with strong consistency. Answer: A multi-region Spanner configuration (or Cloud SQL cross-region read replicas with a documented promotion runbook) — the workload needs to survive a regional, not just a zonal, failure.

Scenario 3: A company wants to minimize cost for a small internal reporting tool used only by employees on one office floor, with no availability requirement beyond business hours. Answer: A single zonal VM is appropriate — spending on regional or multi-regional redundancy would be over-engineering for the stated requirement.

Common Traps

Assuming a regional resource automatically also protects against a regional outage — it does not; regional resources are built to survive a zone failure inside one region, not the loss of the entire region.

Forgetting that a Regional Persistent Disk needs to be explicitly created as regional ( --replica-zones ) — attaching a zonal disk to instances in two zones does not make it regionally redundant.

Over-provisioning multi-region architectures for workloads whose actual availability requirement (as stated in the scenario) is much lower — the exam rewards matching the architecture to the stated requirement , not defaulting to the most redundant option every time.

Key Takeaways

Google Cloud organizes infrastructure into 43 regions and 130 zones (mid-2026); zones within a region share low-latency links, enabling synchronous cross-zone replication.

Zonal resources have no built-in failure protection; regional resources (spanning 2+ zones) survive a single zone outage; multi-regional resources survive a full region outage.

Compute Engine's SLA moves from 99.5% (single zone) to 99.99% (regional, multi-zone) — memorize this jump, since ACE scenario questions often hinge on matching the stated availability requirement to the cheapest architecture that meets it.

Compute Engine SLA by Deployment Pattern