Google ACE Deploying and Implementing a Cloud Solution 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.

• ✗

  Set the --ingress=all flag on the Cloud Run service

  Why it's wrong here

  Setting the --ingress=all flag on the Cloud Run service only controls whether the service accepts public internet traffic; it does not configure any DNS records, TLS certificates, or routing rules. This flag is about network access, not about mapping a custom domain or reducing latency across global regions. Since the service can already be set to allow all traffic by default, this option has no effect on the stated requirements.

• ✗

  Use Cloud CDN to cache content

  Why it's wrong here

  Cloud CDN caches responses at Google's edge locations to reduce latency for repeated requests, but it does not bind a custom domain to the Cloud Run service. To use Cloud CDN, you must place it behind a global external HTTPS load balancer; by itself it provides no custom domain mapping or first-request latency improvement. The fundamental requirements of domain mapping and global low latency still need a load balancer and per-region deployments.

• ✓

  Configure a custom domain mapping on the Cloud Run service

  Why this is correct

  Custom domain mapping on Cloud Run registers the domain and provisions a Google-managed TLS certificate so the domain points to the service's default URL. This is a mandatory step to expose the application at the customer's chosen domain. While it handles the domain mapping, it does not by itself provide multi-region low latency; that requires a global load balancer with multiple regional backends.

• ✓

  Deploy the Cloud Run service in multiple regions and use a multi-regional load balancer

  Why this is correct

  Deploying the Cloud Run service in multiple regions and configuring a multi-regional (global external) load balancer is a valid architecture for global low latency. The load balancer terminates traffic on Google's anycast IP and routes to the nearest healthy region's Cloud Run service via Serverless NEGs. For the custom domain, you would point the domain's A/AAAA record to the load balancer's IP and then set up domain mapping on the load balancer rather than directly on the Cloud Run service.

• ✗

  Deploy the service as a Cloud Run for Anthos on GKE

  Why it's wrong here

  Deploying the service as Cloud Run for Anthos on GKE is not necessary for a managed Cloud Run application that needs a custom domain and global low latency. It adds cluster management overhead and still requires an external load balancer for global distribution. Cloud Run managed, combined with a global HTTPS load balancer, is a simpler and fully managed alternative that meets the same requirements.

Go deeper

Related to this question