Answer-first summary for fast verification
Answer: Deploy Cloud Run services to multiple regions. Create serverless network endpoint groups pointing to the services. Add the serverless NEGs to a backend service that is used by a global HTTP(S) Load Balancing instance.
Option B is correct because it addresses both high availability and low latency requirements for Cloud Run services. Deploying to multiple regions ensures high availability by distributing services across different geographic locations, reducing the impact of regional outages. Using serverless Network Endpoint Groups (NEGs) with a global HTTP(S) Load Balancer enables intelligent traffic routing based on proximity and backend health, minimizing latency for global customers. This approach leverages Google's global load balancing infrastructure, which provides automatic failover and optimal routing. Option A is incorrect because Cloud Run is a regional service, not zonal, and Cloud Endpoints are not the recommended backend for global load balancing with Cloud Run. Option C is suboptimal as Cloud DNS does not support latency-based routing and lacks the dynamic traffic management capabilities of global load balancing. Option D is incorrect because TCP/IP load balancing operates at layer 4, not suitable for HTTP-based RESTful microservices, and Cloud Run endpoints should use serverless NEGs, not direct endpoint attachment.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
To ensure high availability and low latency for containerized RESTful microservices running on Cloud Run for TerramEarth customers, what deployment configuration should you implement?
A
Deploy Cloud Run services to multiple availability zones. Create Cloud Endpoints that point to the services. Create a global HTTP(S) Load Balancing instance and attach the Cloud Endpoints to its backend.
B
Deploy Cloud Run services to multiple regions. Create serverless network endpoint groups pointing to the services. Add the serverless NEGs to a backend service that is used by a global HTTP(S) Load Balancing instance.
C
Deploy Cloud Run services to multiple regions. In Cloud DNS, create a latency-based DNS name that points to the services.
D
Deploy Cloud Run services to multiple availability zones. Create a TCP/IP global load balancer. Add the Cloud Run Endpoints to its backend service.