AZ-400 Question 279
Select 2You are a DevOps engineer responsible for monitoring a new microservices-based solution running on Azure Kubernetes Service (AKS). The solution includes multiple containerized workloads that generate logs and telemetry data. Your goal is to get real-time insights into container performance, application telemetry, and to configure proactive alerts for any issues. Which two actions should you take to establish a robust monitoring approach?
- A
Enable Container Insights in Azure Monitor for the AKS cluster
- B
Store logs locally on each container� ephemeral storage
- C
Integrate your microservices with Azure Application Insights for deeper telemetry
- D
Rely solely on Azure Resource Health to track container performance
- E
Use an internal Azure DevOps Pipeline stage to transfer logs to an on-premises file server
Show answer and explanation
Correct answers: A, C
Explanation
A robust monitoring strategy for AKS-based microservices typically involves enabling Container Insights (part of Azure Monitor) to capture real-time metrics and logs at the container level, and integrating application-level telemetry (e.g., using Application Insights) for deeper performance and diagnostics data. Microsoft� documentation recommends combining these services to obtain comprehensive insight into container health, resource usage, and end-to-end application behavior. Refer to the official Azure documentation on Container Insights (https://learn.microsoft.com/azure/azure-monitor/containers/container-insights-overview) and Application Insights (https://learn.microsoft.com/azure/azure-monitor/app/app-insights-overview) for more details.
- A. Correct.
Enabling Container Insights in Azure Monitor for your AKS cluster allows you to collect metrics and logs at the container level, providing visibility into resource usage and health. This approach is essential for diagnosing performance issues in real-time and setting up alerts for critical conditions.
- B. Incorrect.
Relying on ephemeral storage inside the container is a poor practice. Because ephemeral storage is lost when a container re-deploys or crashes, this choice does not provide a persistent, reliable logging solution.
- C. Correct.
Integrating microservices with Azure Application Insights enables advanced telemetry collection, including distributed transaction tracing, performance metrics, and exception diagnostics. This gives developers and operators a comprehensive view of how the application is functioning in production.
- D. Incorrect.
Azure Resource Health provides availability and status information primarily at the Azure resource level (e.g., the VM or container host), but does not provide granular container performance metrics or application-level telemetry. Alone, it is not sufficient for comprehensive monitoring of container workloads.
- E. Incorrect.
While you can back up or archive logs elsewhere, relying on an internal pipeline stage to store logs on-premises is typically not the most effective way to achieve real-time monitoring and alerting. It also complicates scaling and maintenance.