Google Professional Cloud DevOps Engineer
Get started today
Ultimate access to all questions.
You are managing a critical API deployed on Cloud Run that handles an average of 10,000 requests per minute. To align with user expectations, you must establish Service Level Objectives (SLOs) for availability (99.9%) and latency (95% of requests under 200ms). Additionally, you need to implement active monitoring and measurement of these SLOs. What steps should you take?
You are managing a critical API deployed on Cloud Run that handles an average of 10,000 requests per minute. To align with user expectations, you must establish Service Level Objectives (SLOs) for availability (99.9%) and latency (95% of requests under 200ms). Additionally, you need to implement active monitoring and measurement of these SLOs. What steps should you take?
Explanation:
The question outlines the need to define Service Level Objectives (SLOs) for both availability and latency for a critical API running on Cloud Run, with specific user expectations. Option A suggests configuring Cloud Monitoring for alerts based on latency and error rate, but it does not explicitly mention setting SLOs, which is a key requirement. Option B focuses solely on latency, ignoring the availability requirement, which is not aligned with the user expectations. Option C proposes SLOs that do not meet the user's specified expectations of 99.9% availability and a maximum latency of 200 milliseconds for 95% of requests. Option D correctly addresses the requirement by suggesting to set SLOs using availability and latency service level indicators and using Cloud Monitoring to track these SLOs and alert on violations, which aligns with the user's expectations and the need for active monitoring and measurement.