Cloud Digital Leader Fundamental Cloud Concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Compute Engine with regional load balancers

  Why it's wrong here

  Regional external load balancers are scoped to a single region and use a regional IP address in that region. A global web app requires an anycast global IP that routes users to the nearest available backend; with a regional LB, users on other continents must traverse long networks to the LB region, causing higher latency and no cross-region failover. Because it cannot automatically route to a different region if the LB's region fails, it does not satisfy global low-latency delivery requirements.

• ✗

  Cloud Run with Cloud NAT

  Why it's wrong here

  Cloud NAT gives resources without public IPs outbound internet access via source NAT, enabling them to reach the internet. It does not accept inbound traffic, provide any load balancing across regions, or cache content at edge PoPs. Although Cloud Run is serverless and scalable, pairing it with Cloud NAT alone means requests still arrive directly at the service without geographic routing, so users far away see high latency and there is no global edge caching.

• ✓

  Cloud Load Balancing (global) with Cloud CDN

  Why this is correct

  Cloud Load Balancing uses a single anycast IPv4/IPv6 address to route traffic via Google's global network to the closest region with available backend capacity, enabling global load distribution. Cloud CDN then caches static and dynamic content at over 100 edge locations worldwide, drastically reducing latency and offloading requests from the origin. The global external HTTP(S) load balancer automatically handles failover across regions, scales to millions of QPS, and integrates with CDN for cacheable content — making this the correct choice for a global web app.

• ✗

  Cloud DNS with Traffic Director

  Why it's wrong here

  Cloud DNS provides public DNS resolution, mapping domain names to IP addresses, but it does not route user traffic or provide load balancing. Traffic Director is a control plane for service mesh traffic (e.g., Envoy proxies) that manages East-West traffic policies within a mesh, not a global load balancer and not a CDN. Together they can resolve a name and inform mesh routing, but they cannot deliver content from edge caches or choose the closest healthy region based on IP anycast for inbound HTTPS traffic.

Go deeper

Related to this question