Topic 0 Question 2
For this question, refer to the TerramEarth case study. You have broken down a legacy monolithic application into a few containerized RESTful microservices. You want to run those microservices on Cloud Run. You also want to make sure the services are highly available with low latency to your customers. What should you do?
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.
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.
Deploy Cloud Run services to multiple regions. In Cloud DNS, create a latency-based DNS name that points to the services.
Deploy Cloud Run services to multiple availability zones. Create a TCP/IP global load balancer. Add the Cloud Run Endpoints to its backend service.
ユーザの投票
コメント(17)
- 👍 24fahad01hbti2021/08/26
B is correct. Cloud Run is a regional service. To serve global users you need to configure a Global HTTP LB and NEG as the backend. Cloud Run services are deployed into individual regions and to route your users to different regions of your service, you need to configure external HTTP(S) Load Balancing. https://cloud.google.com/run/docs/multiple-regions A network endpoint group (NEG) specifies a group of backend endpoints for a load balancer. A serverless NEG is a backend that points to a Cloud Run, App Engine, or Cloud Functions service. https://cloud.google.com/load-balancing/docs/negs/serverless-neg-concepts
👍 19MaxNRG2021/10/31- 正解だと思う選択肢: B
Had this question on my exam.
👍 6mad3142022/04/25
シャッフルモード