You have deployed an application on Anthos clusters (formerly Anthos GKE). According to the SRE practices at your company, you need to be alerted if request latency is above a certain threshold for a specified amount of time. What should you do?

The correct answer is to install Anthos Service Mesh and use the Google Cloud Console to define an SLO and alerting policy. Anthos Service Mesh (ASM) provides deep insights into service performance, including latency metrics, and integrates directly with Cloud Monitoring for SLO creation and alerting. This allows you to define a target for latency and automatically trigger alerts when that target is not met over a specified period. Enabling the Cloud Trace API and using Cloud Monitoring alerts based on Cloud Trace metrics is incorrect because while Cloud Trace provides detailed latency data for individual requests, it's not designed for defining aggregate SLOs and alerting on sustained breaches across a service in the same way ASM and Cloud Monitoring SLOs are. Using Cloud Profiler is incorrect because Cloud Profiler is primarily for CPU, memory, and other resource profiling, not for real-time service latency monitoring and SLO-based alerting. Configuring Anthos Config Management (ACM) to deploy a YAML file for SLOs and alerting policies is incorrect. While ACM manages configurations, SLOs and alerting policies are defined within Cloud Monitoring, which integrates with ASM, rather than being directly deployed as Kubernetes YAML resources via ACM.