Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions

Answer analysis

Option-by-option breakdown

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

• ✓

  Deploy additional instances in multiple regions and use a global HTTP(S) load balancer with Cloud CDN.

  Why this is correct

  Deploying additional regional instances behind a global HTTP(S) load balancer uses Google's anycast IP to route each user to the nearest healthy backend, dramatically cutting network round-trip time. Cloud CDN then caches video segments at edge locations, so repeated views are served from the edge, not the origin, reducing latency and origin load. This combination uniquely provides both global latency reduction and the ability to absorb traffic spikes by distributing capacity across multiple regions.

• ✗

  Use Cloud Run for the application and enable automatic scaling globally.

  Why it's wrong here

  Cloud Run is a regional compute service; each service and revision runs in a single chosen region, and its autoscaling mechanism adds instances only within that region's resource pool. There is no built-in feature to automatically replicate a Cloud Run service across regions or route traffic based on user geography. Merely enabling autoscaling does not create a global deployment; you would still need to manually deploy to multiple regions and front them with a global load balancer, so this option is incorrect for global scalability and latency.

• ✗

  Move the application to Google Kubernetes Engine and use horizontal pod autoscaling.

  Why it's wrong here

  Horizontal pod autoscaling (HPA) in Google Kubernetes Engine adjusts the number of pod replicas within a single cluster, and that cluster is confined to a specific zone or region. HPA does not provide any inter-region traffic routing, anycast IP, or proximity-based load balancing, so users far from the cluster continue to experience high latency. Even a regional cluster's endpoint remains tied to its region unless you explicitly configure a multi-cluster ingress behind a global load balancer, which HPA alone cannot do.

• ✗

  Increase the machine type of existing instances and add more instances in the same region.

  Why it's wrong here

  Increasing the machine type of existing instances (vertical scaling) and adding more instances in the same region only increases compute capacity within a single geographic location. It does not shrink the network distance between remote users and the region, so latency for distant clients stays unchanged. Additionally, concentrating all traffic in one region creates a single point of failure, and this approach does nothing to absorb global traffic spikes without overwhelming that single region.

Go deeper

Related to this question