Prepare and test your skills
Prepare and test your skills
Evaluating availability and latency requirements means checking how storage location affects whether data stays reachable and how quickly applications can use it. In Google Cloud, Cloud Storage (opens in a new tab) buckets can be created as zonal, regional, dual-regional, or multi-regional, and each choice changes failure protection and distance between data and users. Regions are independent geographic areas designed as independent failure domains, while zones are deployment areas inside a region that act as single failure domains.
Availability protection by location type describes whether Cloud Storage data remains accessible when a zone or a region has an outage. Zonal storage keeps redundant copies inside one availability zone, so a zonal outage can affect availability. Regional storage replicates data synchronously across availability zones in the same region, while dual-regional and multi-regional storage replicate data asynchronously across geographically separated regions for 99.99% availability.
| Location type | Data redundancy | Failure handling |
|---|---|---|
| Zonal | Redundancy within one availability zone | No protection from a zonal outage |
| Regional | Redundancy across zones with synchronous replication | Automated failover and failback on zonal failure with recovery time objective (RTO) = 0 and no change to storage paths |
| Dual-regional | Redundancy across two regions with asynchronous replication | Automated failover and failback on regional failure with RTO = 0 and no change to storage paths |
| Multi-regional | Redundancy across regions with asynchronous replication | Automated failover and failback on regional failure with RTO = 0 and no change to storage paths |
Dual-regional buckets offer higher availability than regional buckets for the same storage class and support Turbo replication, which replicates 100% of newly written objects between the paired regions within 15 minutes. Multi-regional buckets also provide higher availability than regional buckets for the same storage class through cross-region replication. In both cases, the application keeps using the same bucket path after failover because Google Cloud manages redirection automatically.
Latency and placement relative to compute describes the network delay between the application that reads or writes data and the location where that data is stored. Colocating application components within the same region generally minimizes network latency between components, which can improve application performance and user experience. A zonal bucket offers the highest performance in Cloud Storage for demanding workloads because compute and storage are closest together inside one zone.
Regional storage provides low latency when the application runs in the same region, and reads inside the same region avoid cross-region network hops. Dual-regional storage allows reads from within either of its two regions without leaving that local path, which helps applications that operate in two regions. Protection against a full regional outage uses asynchronous replication across regions, so it comes with replication delay rather than the synchronous zone-to-zone copy used inside a region.
Matching location type to application needs means choosing the smallest failure scope that still meets uptime goals and the closest placement that still meets speed goals. An application that must keep running through a regional outage needs cross-region redundancy, while an application that only needs to survive a zonal outage can use regional protection. An application with strict speed needs should place storage in the same zone or region as its compute, especially when products require it, such as a Compute Engine instance that can only attach a persistent disk in the same region.
A decision tree that starts from workload needs and branches through availability, latency, and geographic scope to pick between zonal, regional, dual-regional, and multi-regional Cloud Storage buckets.
Exam tip: Regional storage survives a zonal failure with RTO = 0, while dual-regional and multi-regional storage survive a regional failure with RTO = 0; only zonal storage can be affected by a single zonal outage.
The Cloud Storage (opens in a new tab) bucket location type defines where object data is stored and how it is protected. The location is chosen when the bucket is created and is permanent, so geographic spread, redundancy, and cost must be balanced up front. The four types are zonal, regional, dual-regional, and multi-regional.
Zonal storage keeps Cloud Storage data redundant within a single availability zone. A zonal outage can affect availability because copies do not exist in another zone. This type offers the highest performance in Cloud Storage for demanding workloads, but it also carries the highest storage price of all location types and has zonal bucket-specific data transfer charges.
Regional storage keeps Cloud Storage data redundant across multiple availability zones within one region. Writes are replicated synchronously between zones, and recovery time objective (RTO) equals 0 because failover and failback after a zonal failure are automatic with no need to change storage paths. Regional storage has the lowest storage price, has no replication charges, and has no outbound data transfer charges when data is read inside the same region, which rewards keeping compute and storage colocated in that region.
Dual-regional storage keeps Cloud Storage data redundant across two specific regions. Replication between the two regions is asynchronous, and RTO equals 0 because failover and failback after a regional failure are automatic with no need to change storage paths. An optional Turbo replication feature can complete replication within 15 minutes for faster protection across the paired regions.
Dual-regional storage provides higher availability than regional storage for the same storage class. It has the highest storage price, adds replication charges on write, and has no outbound data transfer charges when data is read within either of the two regions.
Multi-regional storage keeps Cloud Storage data redundant across multiple regions in a large geographic area. Replication between regions is asynchronous, and RTO equals 0 because failover and failback after a regional failure are automatic with no need to change storage paths. Multi-regional storage provides higher availability than regional storage for the same storage class and serves users spread over a wide area.
Multi-regional storage costs more than regional storage but less than dual-regional storage. Replication charges apply on write, and outbound data transfer charges always apply when reading data, even inside the multi-region footprint.
Comparing location types by availability and cost shows the tradeoff between where copies live and what is paid for storage, replication, and reads.
| Location type | Redundancy and failover | Price and transfer |
|---|---|---|
| Zone | Redundancy within one availability zone; zonal outage can affect availability | Highest performance at highest storage price; zonal-specific transfer charges apply |
| Region | Redundancy across zones with synchronous replication; automatic failover on zonal failure with RTO=0 | Lowest storage price; no replication charges; no outbound charges for reads inside same region |
| Dual-region | Redundancy across two regions with asynchronous replication; automatic failover on regional failure with RTO=0; Turbo replication within 15 minutes | Highest storage price; replication charges on write; no outbound charges for reads within either region |
| Multi-region | Redundancy across regions with asynchronous replication; automatic failover on regional failure with RTO=0 | Higher than region but lower than dual-region; replication charges on write; outbound charges always apply on reads |
Choose zonal when a single-zone workload needs maximum performance and can accept lower availability. Choose regional when cost control and data locality in one region matter most. Choose dual-regional when two regions need shared high availability and free reads in either region. Choose multi-regional when availability across a broad geography matters more than minimizing read transfer cost.
Exam tip: Regional storage has the lowest storage price with no replication charges, while dual-regional storage has the highest storage price with replication charges on write.
Cost and compliance implications of storage locations describe how the choice of where data lives affects both what is paid and whether legal rules are met. In Google Cloud, Cloud Storage (opens in a new tab) buckets use zonal, regional, dual-regional, and multi-regional locations with different pricing structures. Cloud SQL (opens in a new tab) instances use regional placement plus policy controls to keep data residency compliant. A bucket location is permanent when the bucket is created, so the cost and compliance tradeoff must be decided up front.
Storage pricing by location type varies across storage price, replication charges, and data transfer charges for reads. Regional storage is the lowest-cost option for data that can stay in one region, while dual-regional and multi-regional storage add replication cost to keep copies in more than one region. Zonal storage is designed for demanding workloads that need the highest performance in Cloud Storage.
| Location type | Storage price | Replication charges | Read transfer charges |
|---|---|---|---|
| Zone | Highest performance at highest storage price out of all location types | Zonal bucket-specific data transfer charges apply | Zonal bucket-specific data transfer charges apply |
| Region | Lowest storage price | No replication charges | No outbound charges when reading data inside the same region |
| Dual-region | Highest storage price | Replication charges apply on write | No outbound charges when reading data within either region |
| Multi-region | Higher than regions, but lower than dual-regions | Replication charges apply on write | Outbound charges always apply when reading data |
The pricing structure creates a direct tradeoff between cost and geographic spread. Data flows from the writer to replicated copies on every write in dual-regional and multi-regional buckets, which adds replication charges that a regional bucket avoids. Reads stay free of outbound charges only when the reader and the data share the same region for regional buckets, or the same pair of regions for dual-regional buckets, while multi-regional reads always incur outbound charges.
Exam tip: Choose regional storage for the lowest storage price with no replication charges, while dual-regional storage carries the highest storage price with replication charges on write.
Data residency and policy controls for compliance determine the physical location of data plus the local regulations that govern how that data is stored, encrypted, and accessed. Administrators must know the physical location of data centers to research which data locality laws apply, because personally identifiable information (PII) must be stored and processed according to the rules of that region. Examples include a country that mandates government-related data stay inside that country, or a customer contract that requires data for certain users to stay in a different country.
Cloud SQL supports compliance by letting the instance region control where data rests and who can reach it. The region is selected when the Cloud SQL instance is created and can be changed by editing an existing instance, and Google stores data at rest only in the configured regions, including backups. A cross-region read replica places a readable copy in a designated region to help meet residency standards for that region, while network controls limit the locations where users can access data and limit administrator access. Organizational policy constraints enforce these choices at the organization, folder, or project level by defining the Google Cloud locations where users can create resources for supported services, so new resources cannot be placed outside allowed boundaries.
Choose zonal Cloud Storage when a single-zone workload needs the highest storage performance in Cloud Storage and can tolerate reduced availability during a zonal outage. Choose regional Cloud Storage when a workload runs in one region, needs protection against a zonal failure with automatic failover and recovery time objective (RTO) equal to 0, and benefits from low latency and the lowest storage price with no replication charges. Zonal storage keeps redundant copies within one availability zone with no protection from a zonal outage, while regional storage replicates synchronously across zones and has no outbound charges for reads inside the same region.
Dual-regional Cloud Storage keeps data redundant across two specific regions while multi-regional Cloud Storage keeps data redundant across multiple regions in a large geographic area, and both replicate asynchronously across regions with automatic failover and recovery time objective (RTO) equal to 0 on regional failure. Both provide higher availability than regional storage for the same storage class and add replication charges on write. Dual-regional storage has the highest storage price with no outbound charges for reads within either region and supports Turbo replication within 15 minutes, while multi-regional storage costs more than regional but less than dual-regional and always incurs outbound charges on reads.
Colocating application components within the same region generally minimizes network latency between components, so regional storage provides low latency when the application runs in the same region and reads inside the same region avoid cross-region network hops. A zonal bucket offers the highest performance in Cloud Storage for demanding workloads because compute and storage are closest together inside one zone. Dual-regional storage allows reads from within either of its two regions without leaving that local path, while protection against a full regional outage uses asynchronous replication across regions with replication delay.
Cloud SQL lets the instance region control where data rests, and Google stores data at rest only in the configured regions, including backups. A cross-region read replica places a readable copy in a designated region to help meet residency standards for that region, while network controls limit access locations and organizational policy constraints define allowed Google Cloud locations for resource creation. Administrators must still know the physical location of data centers because personally identifiable information (PII) must be stored and processed according to the rules of that region, such as country mandates or customer contracts.
A data analytics team is configuring a new Cloud SQL instance in the us-central1 region to support business intelligence dashboards. The team needs to ensure the database automatically fails over if a single data center zone experiences an outage, while keeping compute resources within the same geographic region to minimize network latency and cross-region egress costs.
Which storage location availability configuration should the team select for the Cloud SQL instance?
Last updated