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 global enterprise hosts a latency-sensitive web application in us-central1 and europe-west1 serving end users across North America, Europe, and Asia-Pacific. Currently, each region uses a Regional external Application Load Balancer on the Standard Tier with Cloud DNS routing, and outbound responses exhibit high latency and inconsistent packet loss. During a recent regional transit outage, the operations team attempted to reclassify the Standard Tier external IP addresses to Premium Tier as a failover measure, which failed to improve routing.
You need to redesign the network architecture to meet the following requirements:
Which network architecture should you implement?
us-central1 and europe-west1, and enable Cloud CDN on the backend service.Premium Tier delivers external traffic between internet users and Google Cloud workloads over Google's private, low-latency global fiber backbone spanning over 200 edge points of presence (PoPs) worldwide. Pairing Premium Tier with a Global external Application Load Balancer places a single, globally announced anycast IP address in front of multi-region backends, terminating client connections at Google Front Ends (GFEs) located near end users.
us-central1 or europe-west1 during a regional outage without waiting for DNS TTL expiration. Premium Tier also provides a 99.99% uptime SLA for Compute Engine VMs.Unlike Standard Tier or regional load balancers, this design combines edge termination, Cloud CDN, backbone egress routing, and single-IP multi-region resilience in one managed architecture.
A Classic Application Load Balancer operates as a global load balancer when deployed in Premium Tier, but functions strictly as a regional load balancer when configured in Standard Tier. In Standard Tier, it uses regional external IP addresses to route HTTP(S) traffic to backends in a single region through local ISP transit and peering links.
The workload was non-latency-sensitive, confined to a single region, did not require Cloud CDN or a 99.99% SLA, and had no expectation of dynamic failover to Premium Tier during outages.
us-central1 and europe-west1 using Premium Tier regional external IP addresses, enable Cloud CDN, and configure Cloud DNS routing policies for multi-region failover.A Regional external Application Load Balancer is a managed Layer 7 proxy deployed within a single Google Cloud region that connects exclusively to backends in that same region. When paired with a Premium Tier regional external IP address, traffic travels over Google's global backbone to and from edge PoPs close to users, rather than traversing public transit networks near the origin region.
The organization had strict regional compliance mandates requiring TLS termination inside each specific region, did not require Cloud CDN, and could tolerate DNS-based failover times instead of single-IP anycast failover.
Standard Tier is a cost-optimized network tier that routes external traffic over public ISP and transit networks close to the Google Cloud region where the resource is deployed. A Global external proxy Network Load Balancer is a Layer 4 reverse proxy that terminates TCP/SSL connections at Google's network edge and distributes traffic across multi-region backends using a global anycast IP address.
No such configuration exists because Global external proxy Network Load Balancers and Cloud CDN both require Premium Tier; it would only be viable if Premium Tier and a Global external Application Load Balancer were used instead.
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