Google Professional Cloud DevOps Engineer Question 159
Select 3Google Cloud PlatformYour team manages a globally distributed e-commerce application hosted on Google Cloud. Users in certain regions are reporting high latency during peak traffic hours. You suspect the issue might be related to inefficient load balancing and the geographical placement of resources. What actions should you take to address the performance and latency issues?
- A
Enable Cloud CDN on your load balancers to cache static content closer to users.
- B
Configure a multi-region deployment for your backend services using Cloud Run or GKE.
- C
Implement a latency-based routing policy in Cloud DNS to direct users to the nearest region.
- D
Increase the CPU and memory resources for instances in the current region to handle peak traffic.
- E
Set up a custom monitoring dashboard in Cloud Monitoring to track latency metrics and user traffic patterns.
Show answer and explanation
Correct answers: A, B, C
Explanation
Addressing performance and latency issues in a globally distributed application requires optimizing resource placement, caching, and routing strategies. By enabling Cloud CDN, configuring multi-region deployments, and implementing latency-based routing, you can significantly reduce latency for end users. Increasing resources in a single region or monitoring traffic patterns are supplementary actions but do not directly resolve the root cause of geographical latency.
- A. Correct.
Enabling Cloud CDN helps cache static content at the edge, reducing latency for users by serving content from locations closer to them.
- B. Correct.
Deploying backend services in multiple regions ensures that user requests are handled by servers closer to their geographic location, reducing latency and improving performance.
- C. Correct.
Latency-based routing in Cloud DNS directs users to the nearest available region, ensuring faster response times and improved user experience.
- D. Incorrect.
While increasing resources in the current region might improve performance temporarily, it doesn't address the core issue of global latency caused by geographical distance.
- E. Incorrect.
Setting up a monitoring dashboard is useful for diagnosing issues, but it doesn't directly resolve the latency and performance problems.