Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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:
us-central1).Which Network Service Tier configuration should the DevOps team implement to achieve the lowest overall egress cost while satisfying all technical and architectural requirements?
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.
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.
This option proposes placing the batch export workload on Premium Tier under the premise of avoiding ISP peering charges, while configuring the global web application on Standard Tier using classic proxy Network Load Balancers.
Workload 1 required strict low-latency guarantees across global destinations and Workload 2 had no CDN, Anycast, or 99.99% SLA requirements.
This option suggests deploying Workload 2 on Standard Tier using regional external IPv6 addresses while assuming Standard Tier provides a 99.99% network SLA.
Standard Tier supported external IPv6 allocations and provided four-nines (99.99%) SLA terms, neither of which is supported in Google Cloud.
This option attempts to standardize both workloads onto Standard Tier to reduce data transfer costs across all services, while trying to attach Cloud CDN and a Global external Application Load Balancer to the global web application.
Workload 2 did not require Cloud CDN, could operate with independent regional load balancers in each region via external DNS routing, and accepted a 99.9% uptime SLA.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated