An enterprise DevOps team is conducting a FinOps review to optimize network egress spend across multiple Google Cloud workloads without compromising technical constraints. They have identified two distinct services: Workload 1: A latency-insensitive batch data export system that transfers high volumes of data to external partner endpoints on the internet from a single region (us-central1). Workload 2: A mission-critical, globally distributed web application that requires a 99.99% uptime Service Level Agreement (SLA), integration with Cloud CDN, and multi-region backend load balancing behind a single public Anycast IP address. Which Network Service Tier configuration should the DevOps team implement to achieve the lowest overall egress cost while satisfying all technical and architectural requirements?

Assign Standard Tier with regional external IP addresses to Workload 1, and configure Premium Tier with global external IP addresses for Workload 2.: ### What Network Service Tiers Are **Network Service Tiers** in Google Cloud allow organizations to optimize their network connectivity and cost by choosing between **Premium Tier** and **Standard Tier**. Premium Tier routes inbound and outbound traffic through Google's high-speed, private global fiber backbone to and from points of presence (PoPs) closest to the end user. Standard Tier delivers outbound traffic through public transit, peering, and regular ISP networks directly from edge PoPs near the originating Google Cloud region. ### How It Meets Workload Requirements * **Workload 1 (Batch Data Export):** Standard Tier provides cost-effective outbound data transfer pricing compared to Premium Tier. Because the data transfer originates in a single region and is latency-insensitive, using **regional external IPv4 addresses** on Standard Tier allows traffic to be handed off to local transit/peering networks, significantly cutting egress costs without impacting the pipeline's functionality. * **Workload 2 (Global Web App):** Premium Tier provides a **99.99% network uptime SLA**, support for **global external Anycast IP addresses**, multi-region load balancing with Global external Application Load Balancers, and native integration with **Cloud CDN**. ### Key Advantages and Capabilities * **Granular Tier Control:** Network tiers can be configured per resource (e.g., individual forwarding rules, VM instances, or project defaults). * **Cost Efficiency:** Standard Tier reduces outbound data transfer charges for latency-tolerant and region-bound egress. * **Global Backbone Performance:** Premium Tier minimizes packet loss and latency by carrying global traffic across Google's private network across 200+ edge PoPs. * **Service Interoperability:** Advanced features such as Cloud CDN and global external load balancers operate strictly on Premium Tier. ### Why This Is Optimal This architecture precisely aligns infrastructure spending with workload sensitivity. It maximizes financial savings on high-volume batch transfers using Standard Tier while preserving high availability, CDN caching, and Anycast routing for global end users on Premium Tier.

Network Service Tier Selection Cost Optimization | Professional Cloud DevOps Engineer

Network Service Tier Selection Cost Optimization

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise DevOps team is conducting a FinOps review to optimize network egress spend across multiple Google Cloud workloads without compromising technical constraints. They have identified two distinct services:

Workload 1: A latency-insensitive batch data export system that transfers high volumes of data to external partner endpoints on the internet from a single region (us-central1).
Workload 2: A mission-critical, globally distributed web application that requires a 99.99% uptime Service Level Agreement (SLA), integration with Cloud CDN, and multi-region backend load balancing behind a single public Anycast IP address.

Which Network Service Tier configuration should the DevOps team implement to achieve the lowest overall egress cost while satisfying all technical and architectural requirements?

Configure Standard Tier for both workloads, utilizing a Global external Application Load Balancer with Cloud CDN enabled for Workload 2 to lower data transfer rates.

Assign Standard Tier with regional external IP addresses to Workload 1, and configure Premium Tier with global external IP addresses for Workload 2.

Configure Standard Tier with regional external IPv6 addresses for Workload 2, and rely on the Standard Tier 99.99% SLA for high availability.

Assign Premium Tier to Workload 1 to prevent cross-region ISP peering fees, and configure Standard Tier with classic proxy Network Load Balancers for Workload 2.

Professional Cloud DevOps Engineer

Network Service Tier Selection Cost Optimization

Related questions