Answer-first summary for fast verification
Answer: Deploy the Cloud Run services to multiple regions. Create serverless network endpoint groups (NEGs) that point to the services. Create a global HTTPS load balancer, and attach the serverless NEGs as backend services of the load balancer.
To ensure high availability and low latency for Cloud Run services, deploying across multiple regions is essential as it mitigates regional outages. A global HTTPS load balancer with serverless Network Endpoint Groups (NEGs) is the correct approach because serverless NEGs allow the load balancer to route traffic to Cloud Run services, and the global HTTPS load balancer optimizes traffic distribution based on proximity and health checks. Option B correctly combines multi-region deployment, serverless NEGs, and a global HTTPS load balancer. Other options are incorrect: options A and C reference availability zones (Cloud Run abstracts zone management) or improper components (TCP load balancer, Cloud Endpoints), and option D uses DNS round-robin, which lacks intelligent routing and health checks.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have developed a web application using multiple containerized microservices and plan to deploy them on Cloud Run. How can you ensure these services achieve high availability and low latency for your users?
A
Deploy the Cloud Run services to multiple availability zones. Create a global TCP load balancer. Add the Cloud Run endpoints to its backend service.
B
Deploy the Cloud Run services to multiple regions. Create serverless network endpoint groups (NEGs) that point to the services. Create a global HTTPS load balancer, and attach the serverless NEGs as backend services of the load balancer.
C
Deploy the Cloud Run services to multiple availability zones. Create Cloud Endpoints that point to the services. Create a global HTTPS load balancer, and attach the Cloud Endpoints to its backend
D
Deploy the Cloud Run services to multiple regions. Configure a round-robin A record in Cloud DNS.
No comments yet.