AZ-400 Question 280
Single answerYou have an Azure Kubernetes Service (AKS) environment configured to send performance data and container logs to a Log Analytics workspace. You need to set up an alert for high CPU usage on the AKS cluster that automatically triggers a task in your Azure DevOps pipeline whenever the threshold is exceeded. What should you do to achieve this integration?
- A
A. Configure a metric alert in Azure Monitor and set up an Action Group with a webhook pointing to the Azure DevOps pipeline endpoint.
- B
B. Enable Azure Security Center on the AKS cluster and rely on Security Center alerting to call Azure DevOps through an email subscription.
- C
C. Create a runbook in Azure Automation that polls the Log Analytics workspace for CPU spikes and manually triggers the DevOps pipeline.
- D
D. Set up a GitHub Actions workflow to monitor CPU metrics from the AKS cluster and integrate the workflow with Azure DevOps using OAuth.
Show answer and explanation
Correct answer: A
Explanation
To integrate Azure Monitor alerts with Azure DevOps, you configure a metric alert for the AKS cluster� CPU usage in Azure Monitor. Then, you create an Action Group that uses a webhook to notify your Azure DevOps pipeline endpoint whenever the alert is triggered. This best practice approach is documented in Microsoft� official Azure Monitor and Azure DevOps integration guides. By handling thresholds and notifications natively within Azure Monitor and using webhooks for DevOps actions, you establish a seamless connection between performance monitoring and automated pipeline tasks.
- A. Correct.
A. Correct. Setting up a metric alert in Azure Monitor and configuring an Action Group with a webhook pointing to the Azure DevOps pipeline endpoint is the recommended way to automatically trigger responses in Azure DevOps. You first create a metric alert for CPU usage, then define an Action Group that includes a webhook. This webhook sends the alert details to Azure DevOps, enabling a task to run when thresholds are exceeded.
- B. Incorrect.
B. Incorrect. While Azure Security Center can raise alerts for security issues, it is not the primary solution for forwarding operational or performance alerts back to Azure DevOps. Its focus is on security and compliance rather than performance metrics like CPU usage.
- C. Incorrect.
C. Incorrect. While using Azure Automation and a runbook could theoretically query Log Analytics, it is a more manual and less efficient process. Azure Monitor� native metric alert with an Action Group is a more direct and automated approach.
- D. Incorrect.
D. Incorrect. GitHub Actions is a separate CI/CD platform. Integrating GitHub Actions to pull AKS metrics and then bridging to Azure DevOps is overly complex and not the intended solution when working solely within Azure DevOps and Azure Monitor capabilities.