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.
You are designing a hybrid and multi-cloud network in a single Google Cloud project connecting an on-premises data center, AWS (us-east-1), and Google Cloud (us-central1 and europe-west1). Your design must meet these requirements:
us-central1 Compute Engine VMs over the internet at the lowest egress cost, accepting a 99.9% SLA.Which Network Service Tiers configuration should you implement?
Setting the project default to Standard Tier causes newly created external IP addresses without an explicit resource-level override to use Standard Tier routing, sending internet traffic over regional peering and ISP transit networks rather than Google's global backbone. Deploying a Regional external Application Load Balancer confines load balancing and TCP/TLS termination to a single Google Cloud region.
us-central1, europe-west1, and AWS us-east-1.Using Standard Tier as a project default with a Regional external Application Load Balancer would be appropriate for cost-sensitive, single-region web workloads that do not require Cloud VPN, global anycast routing, or a 99.99% availability SLA.
This configuration places the us-central1 VMs in Standard Tier while assuming a Premium Tier project default acts as an automatic failover path during ISP disruptions. It also attempts to deliver the multi-cloud API using a Classic Application Load Balancer configured in Standard Tier.
us-central1, europe-west1, and AWS.A Classic Application Load Balancer in Standard Tier is suitable only for legacy, single-region HTTP(S) applications that do not require global backends, hybrid multi-region routing, or automatic backbone failover.
Google Cloud Network Service Tiers allow you to optimize external network paths independently at the project level or resource level. When both are specified, the resource-level tier takes precedence, enabling hybrid and multi-cloud architectures to combine Premium Tier and Standard Tier within the same VPC and project.
us-central1, europe-west1, and AWS us-east-1.us-central1 batch-export VMs overrides the project default. Outbound traffic exits Google's network via local peering or ISP transit networks near us-central1, lowering egress costs while providing the 99.9% VM uptime SLA.us-central1 rather than traversing the global backbone.Unlike applying a single tier across the entire project, granular resource-level selection satisfies every SLA, routing path, and cost constraint simultaneously without overpaying for non-critical internet egress.
Leaving every Compute Engine VM on Premium Tier routes all outbound batch traffic from us-central1 across Google's global private backbone to an edge Point of Presence (PoP) closest to the partner's destination network. Attempting to configure Standard Tier directly on a Cloud Storage bucket assumes storage buckets expose a standalone tier toggle independent of load balancing.
us-central1 batch-export VMs on Premium Tier incurs higher Premium Tier internet egress charges for large, non-latency-sensitive transfers instead of leveraging Standard Tier local ISP transit pricing.Using Premium Tier across VMs and direct Cloud Storage access is appropriate when partner exports are latency-sensitive, require a 99.99% SLA, and justify higher global backbone egress costs.
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