Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A media company operates three projects under a single Cloud Billing account and wants to optimize outbound network egress costs in us-central1 without violating architectural or SLA requirements:
150 GB/month per project to internet partners) and 5 TB/month of VM-to-VM replication to europe-west1.How should the network architect configure Network Service Tiers and forecast the resulting egress charges?
us-central1 and unchanged inter-region VM egress to europe-west1.Google Cloud Network Service Tiers can be configured granularly at the resource level (such as on an individual VM's external IP address or a load balancer forwarding rule), which takes precedence over any project-level default. By combining Premium Tier for performance-critical global delivery and Standard Tier for cost-sensitive regional exports, an organization aligns network spend directly with workload requirements.
0, 1,024, and 10,240 GiB). Because usage aggregates at the Cloud Billing account level per SKU, 15 TiB (15,360 GiB) qualifies for the highest volume discount tier.us-central1 generate 450 GB/month combined (3 × 150 GB), the first 200 GB is free and the remaining 250 GB is billed at lower Standard Tier internet egress rates.us-central1 to europe-west1) always stays on Google's private network regardless of the selected Network Service Tier, so inter-region VPC egress charges remain unchanged.This configuration balances budget constraints against performance and SLA requirements while accurately reflecting how Google Cloud aggregates tiered egress SKUs, enforces regional Free Tier limits across projects, and bills internal inter-region traffic.
europe-west1 by routing it over public ISP peering.This option correctly retains Premium Tier for Workload 1 and places Workload 2 VMs on Standard Tier, but assumes that splitting workloads across three projects multiplies the 200 GB Free Tier and shifts inter-region VM-to-VM replication onto cheaper public ISP paths.
200 GB of free usage per month per region across all projects in a billing account on a per-SKU basis—not 200 GB per project. Because the three projects collectively send 450 GB/month from us-central1, they exceed the 200 GB regional cap and will incur Standard Tier egress charges for the remaining 250 GB/month.us-central1 to europe-west1) always remains on Google's private network regardless of the tier assigned to the VMs' external IPs.us-central1 and europe-west1 incurs standard inter-region network egress fees, which cannot be bypassed by changing Network Service Tiers.5 TB/month inter-region replication cost, the architect would need to compress payloads, optimize replication frequency, or colocate dependent resources in the same region rather than changing external network tiers.Combined internet egress across all three projects in us-central1 stayed at or below 200 GB/month, and the forecast accounted for full inter-region VPC egress charges to europe-west1.
This approach attempts to force Standard Tier pricing onto both workloads by placing a regional load balancer and Cloud CDN in front of a multi-regional Cloud Storage bucket, while relying on automated tier reclassification as a failover mechanism for Standard Tier VMs.
5 Gbps of traffic from Standard Tier to Premium Tier even outside of an outage requires prior coordination with an account manager.Workload 1 used a single-region Cloud Storage bucket in the same region as a regional external Application Load Balancer without Cloud CDN, and Workload 2 did not rely on dynamic tier reclassification for outage recovery.
This option applies Standard Tier as the project-level default across all projects to force lower egress rates everywhere, while splitting projects into separate Cloud Billing accounts under the assumption that each account will optimize tiered volume discounts.
10,240+ GiB), increasing the effective per-GiB rate.The organization needed to isolate costs purely for chargeback without caring about volume discounts, and had no latency-sensitive or global CDN/multi-region storage requirements.
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