Regions, dual-regions, multi-regions, and zones as redundancy choices
Google Cloud storage location types (zone, region, dual-region, and multi-region) determine where data is physically stored and how it is replicated for redundancy and availability. Choosing between them involves trade-offs among latency, availability, durability, and compliance/data residency requirements. Understanding these options is essential for designing resilient data architectures with services like Cloud Storage, BigQuery, Bigtable, and Spanner.
Must-know
- A zone is a single physical location within a region; zonal resources (e.g., zonal Persistent Disks) offer lowest latency but no built-in redundancy across failures.
- A region is a specific geographic area containing multiple zones; regional storage (e.g., Cloud Storage regional buckets, regional Persistent Disks) replicates data synchronously across zones within that region for higher availability than zonal.
- A dual-region is a specific pair of regions where data is replicated across both locations, providing geo-redundancy with lower latency than multi-region and, for Cloud Storage, an option for turbo replication with an RPO/RTO SLA.
- A multi-region is a large geographic area (e.g., 'US', 'EU', 'ASIA') spanning multiple regions; Cloud Storage multi-region buckets and BigQuery multi-region datasets replicate data across regions within that area for the highest availability and durability.
- Data residency and compliance requirements often dictate choosing a specific region or dual-region over a broader multi-region to keep data within defined geographic boundaries.
- Higher redundancy (multi-region > dual-region > region > zone) generally increases availability and durability but can increase cost and, in some cases, read/write latency, so location type should match the workload's availability and residency needs.
A media company is designing a Cloud Storage bucket to hold master video files. The compliance team requires that objects be synchronously stored in two specific, named regions (for example, one on the US east coast and one on the US west coast) so the company can predict exactly which two regions hold copies of the data. They also want the option to enable turbo replication to guarantee a 15-minute replication time objective between those two regions. Which storage location type should the team choose for the bucket?
What you have tried across GCP ADP's objectives, not a readiness score.
Data Preparation and Ingestion
- When to load first and when to transform first, and what sits between the two
- Picking a way to move existing data into Google Cloud
- Judging whether a dataset is trustworthy enough to build on
- Fixing messy records before they reach a report
- Telling CSV, JSON, Parquet, Avro, and relational tables apart, and where each fits
- Picking how to pull data out of a source system
- Matching a workload to the right storage or database service
- Getting files and tables loaded with a CLI, a transfer service, or a client library
Data Analysis and Presentation
- Writing BigQuery SQL that answers a reporting question
- Exploring and charting data inside a hosted notebook
- Turning a question from the business into an analysis that settles it
- Building a dashboard and getting it in front of the right people
- Deciding whether a job calls for Looker or for Looker Studio
- Editing LookML to change what a model exposes
- Spotting a problem worth solving with BigQuery ML or AutoML
- Calling a hosted Google language model straight from BigQuery
- Sequencing a machine learning project from raw data to served predictions
- Building, fitting, and scoring a model with SQL alone
- Running predictions against a model you already trained
- Keeping trained models catalogued in one place
Data Pipeline Orchestration
- Matching a transformation job to Dataproc, Dataflow, Dataform, or a managed alternative
- Weighing whether the transform belongs before or after the load
- Assembling the services a simple transformation pipeline needs
- Putting a query on a schedule and keeping it running
- Watching a Dataflow job and spotting where it stalls
- Reading logs and metrics to work out what a pipeline actually did
- Choosing what should drive a multi-step workflow
- Streaming messages into BigQuery as they arrive rather than in batches
- Wiring a trigger so one event starts the next step
Data Management
- Granting only the access a person or service actually needs
- Controlling who can read a bucket, and what uniform access changes
- Sharing a dataset with another team or company without copying it
- Matching a storage class to how often the data gets read
- Expiring old data automatically so it stops costing money
- Picking somewhere to park data that must be kept but is rarely read
- Comparing the managed backup and restore options across services
- Working out when a second copy is worth what it costs
- Regions, dual-regions, multi-regions, and zones as redundancy choices
- Deciding who should hold the encryption keys
- What a key management service does for creating, rotating, and revoking keys
- Protecting data on the wire versus data sitting on a disk
Coverage checked against the published exam guide on Aug 12, 2026.
These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.