Prepare and test your skills

Prepare and test your skills

Implement Tier Selection and Cost Management is the practice of choosing between Premium Tier and Standard Tier for each Google Cloud resource to balance performance against cost. Network Service Tiers (opens in a new tab) controls the path that traffic takes between the internet and Google Cloud workloads. Premium Tier uses Google's global backbone for the best performance, while Standard Tier uses the public internet for a lower price.
Premium Tier is the performance-optimized tier that carries traffic on Google's private fiber network with over 200 points of presence (PoPs). Inbound traffic from an internet user enters Google's network at the PoP closest to that user and travels inside Google's network to the virtual machine (VM) in the Virtual Private Cloud (VPC) network or to the Cloud Storage bucket. Outbound traffic stays on Google's network until it exits at the PoP closest to its destination, which reduces hops and congestion.
Premium Tier supports both regional external IP addresses and global external IP addresses, and all global external IP addresses must use Premium Tier. Applications with backends in more than one region, such as external Application Load Balancers (opens in a new tab) and external proxy Network Load Balancers spanning regions, require Premium Tier. Premium Tier offers a 99.99% uptime service level agreement (SLA) for VMs, where a VM that loses external connectivity for more than a minute counts as downtime.
Standard Tier is the cost-optimized tier that routes traffic over the public internet instead of Google's global backbone. Inbound traffic enters Google's network at a peering or transit PoP near the region of the Standard Tier IP address, not near the user. Outbound traffic normally leaves Google's network from the same region as the sending VM or Cloud Storage bucket, regardless of destination, and is then carried by transit providers and ISPs.
Standard Tier is priced lower than Premium Tier and fits applications that are not sensitive to latency or that keep VMs and storage in a single region. Standard Tier includes a Free Tier of 200 GB of free usage per month in each region you use, measured per SKU across all projects. Standard Tier offers a 99.9% uptime SLA for VMs, which is lower than Premium Tier, so the cost saving comes with reduced performance and reliability guarantees.
Tier selection starts with performance needs, geography, and pricing, and the tier is chosen at the resource level so different resources can use different tiers. If you are not sure which tier fits, choose Premium Tier because it is the default. Use Premium Tier for global users and multi-region backends, and use Standard Tier for single-region, cost-sensitive workloads.
| Tier | Best for | How traffic moves | VM uptime SLA |
|---|---|---|---|
| Premium Tier | Global users and high performance | Enters Google network near the user and exits near the destination | 99.99% |
| Standard Tier | Single region and lower cost | Enters and exits Google network near the resource region over the internet | 99.9% |
The table shows the core tradeoff: Premium Tier keeps traffic longer on Google's backbone for performance, while Standard Tier hands traffic to the internet near the resource region for savings. Standard Tier with Cloud Storage is allowed only when the bucket is a backend of an external Application Load Balancer in the same region, while multi-regional buckets as backends require Premium Tier. You cannot use Premium Tier as a backup for Standard Tier during a Standard Tier outage, and moving more than 5 Gbps from Standard Tier to Premium Tier outside an outage requires contacting your account manager.
The network tier can be set as a project default (opens in a new tab) and overridden for individual resources, and the resource-level setting always wins. The project default applies only to newly created eligible resources and does not change existing resources. Changing the project default therefore affects future VMs, forwarding rules, and static external IP addresses, but existing resources keep their current tier.
For a VM or instance template, the tier is set on its external IP address, and for load balancing the tier is set on the forwarding rule and its external IP address. A regional external passthrough Network Load Balancer in Standard Tier needs both a Standard Tier IP address and a Standard Tier forwarding rule. Classic Application Load Balancers and classic proxy Network Load Balancers in Standard Tier must meet three related requirements:
With Standard Tier, clients from anywhere can still reach the external IP address, but a Google Front End (GFE) terminates the connection in the chosen region and contacts backends only in that region. To serve multiple regions with Standard Tier, you must create a separate regional load balancer with its own regional IP address in each region.
Exam tip: If tiers are set at both levels, the resource-level tier takes precedence over the project-level default, and Premium Tier is the default when nothing is specified.
External IP addresses come from separate pools based on scope and tier, and an address cannot move between pools. In Standard Tier, VMs and load balancers share the Standard Tier regional pool for that region. In Premium Tier, regional passthrough Network Load Balancers and VMs use a Premium Tier regional pool, while external Application Load Balancers and external proxy Network Load Balancers use global addresses from a separate global pool.
Because pools are separate, changing an instance with an ephemeral IP address from one tier to the other also changes its IP address. A Standard Tier regional address cannot be converted to Premium Tier or moved to another region, so changing a load balancer tier requires deleting the forwarding rule and reserving a new IP address of the new tier. Unused Standard Tier addresses are automatically parked, meaning HTTP requests to them can receive a Google-hosted HTTP 404 page instead of being dropped, and a Standard Tier address on a VM can appear parked during a live migration longer than 20 minutes.
Evaluate Resource Compatibility and Global Reach is the task of matching each Google Cloud resource to the network tier that supports where the resource must be reachable. Network Service Tiers (opens in a new tab) offers Premium Tier for global performance and Standard Tier for lower cost with regional delivery. The choice balances requirements and budget, because the tiers differ in network path and geographic reach.
Premium Tier is the network tier that carries traffic on Google's private global backbone for most of the distance. User traffic enters Google's network at the edge location closest to the user, then travels across Google's backbone to the resource's region, and return traffic follows the same path back. This global reach is a requirement for global load balancing services, which distribute traffic to backends in multiple regions from a single global address and depend on Premium Tier to function.
Standard Tier is the network tier that carries traffic over the regular public internet instead of Google's global backbone. User traffic travels over the internet to the Google Cloud region that hosts the resource, so entry and exit stay close to that region rather than close to the user. Because of this regional behavior, Standard Tier configurations are constrained to regional resources and cannot support services that need a single global frontend across multiple regions.
Resource compatibility is determined by where the resource must be reachable from. A global load balancer requires Premium Tier because its frontend must accept users worldwide and route them to the best backend region. A regional virtual machine, regional load balancer, or storage bucket in one region can use either tier, with Standard Tier keeping traffic regional and Premium Tier keeping long-distance performance.
| Tier | Network path | Choose when |
|---|---|---|
| Premium Tier | Traffic flows from the user to the closest Google edge, then across Google's backbone to the resource region | The resource is a global load balancing service or needs worldwide reach and consistent performance |
| Standard Tier | Traffic flows from the user over the public internet directly to the resource region | The resource is regional and lower network cost matters more than global performance |
Exam tip: Global load balancing requires Premium Tier, while Standard Tier is limited to regional delivery.
Contrast Routing Paths and Performance Characteristics is the comparison of how Premium Tier and Standard Tier move outbound traffic and how that path affects latency. Network Service Tiers (opens in a new tab) lets you select the network path for traffic leaving Google Cloud. Selecting the right tier balances connectivity needs, performance, and budget.
Premium Tier routing carries outbound traffic on Google's global private fiber network for low-latency delivery. Traffic flows from the Google Cloud region where the resource runs across Google's private backbone to an edge location close to the user, and only then enters the public internet for the final hop to the user. Because most of the journey stays inside Google's managed network instead of public internet transit, latency is lower and more consistent. Premium Tier is designed for global delivery where users are distributed across regions and performance matters more than saving network cost.
Side-by-side architecture showing Premium Tier entering Google's backbone near the user versus Standard Tier traveling over public internet to a peering PoP near the VM region.
Standard Tier routing carries outbound traffic over public internet transit for regional distribution. Traffic flows from the Google Cloud region where the resource runs out to the public internet in that same region, and then travels across third-party internet networks to reach the user. Because performance depends on public internet routing and congestion outside Google's control, latency is typically higher and more variable than Premium Tier. Standard Tier is designed for use cases where users are near the hosting region and lower network cost is more important than global low latency.
The two tiers represent a direct tradeoff between network path and performance outcome. Premium Tier keeps traffic on Google infrastructure longer, while Standard Tier hands traffic to the internet earlier.
| Tier | Routing path | Performance characteristic |
|---|---|---|
| Premium Tier | Traffic travels from the hosting region across Google's global private fiber network and exits close to the user | Low-latency, consistent global delivery |
| Standard Tier | Traffic exits Google's network in the hosting region and travels over public internet transit to the user | Higher, more variable latency focused on regional delivery |
Choose Premium Tier when users are spread across geographies and need fast, reliable access, and choose Standard Tier when users are concentrated near the resource region and cost-efficiency is the priority.
Exam tip: Premium Tier exits Google's network close to the user, while Standard Tier exits Google's network in the same region that hosts the resource.
Premium Tier carries traffic on Google's private fiber network with over 200 points of presence (PoPs) for low-latency global delivery, while Standard Tier routes traffic over the public internet for lower cost with higher and more variable latency. Premium Tier traffic enters Google's network near the user and exits near the destination, whereas Standard Tier traffic enters and exits near the resource region. Premium Tier offers a 99.99% uptime service level agreement for a virtual machine (VM), compared to 99.9% for Standard Tier.
Use Premium Tier for global users and multi-region backends that need high performance, and use Standard Tier for single-region, cost-sensitive workloads that are not sensitive to latency. Global load balancing services with backends in more than one region require Premium Tier, while Standard Tier supports only regional resources. If you are not sure which tier fits, choose Premium Tier because it is the default.
Changing between Premium Tier and Standard Tier changes the external IP address because Standard Tier and Premium Tier use separate address pools and an address cannot move between pools. A Standard Tier regional address cannot be converted to Premium Tier or moved to another region, so changing a load balancer tier requires deleting the forwarding rule and reserving a new IP address of the new tier. Changing an instance with an ephemeral IP address from one tier to the other also changes its IP address.
An organization is deploying an external web service hosted on Compute Engine virtual machines in a single region (us-central1). The application serves regional traffic, does not require Cloud CDN, and must minimize outbound network data transfer costs.
Which configuration should the organization implement to achieve this goal?
Last updated