AZ-305 Question 14
Single answerContoso hosts multiple workloads in Azure, including web apps on Azure App Service, containers on Azure Kubernetes Service (AKS), and several Windows-based virtual machines (VMs). They want a unified monitoring strategy to consolidate performance metrics, application telemetry, and logs across all these resources. Additionally, they need the ability to create custom log queries, configure retention policies, and set alerts to quickly troubleshoot cross-service issues. Which solution should you recommend?
- A
Use Azure Monitor with a single Log Analytics workspace and enable Application Insights for the web apps and AKS workloads
- B
Enable Azure Diagnostics at each resource level, sending logs to individual Azure Storage accounts
- C
Deploy a different monitoring service for each resource type to keep logs and metrics separate
- D
Implement only Azure Monitor Metrics without collecting or storing any logs
Show answer and explanation
Correct answer: A
Explanation
In Azure, the recommended practice is to use Azure Monitor for collecting metrics, logs, and telemetry across all resources. Integrating a single Log Analytics workspace allows for centralized storage, querying, and retention management, while Application Insights provides deep insight into application performance. This approach simplifies cross-service correlation and troubleshooting. For more information, refer to Azure Monitor documentation at https://learn.microsoft.com/azure/azure-monitor/.
- A. Correct.
Option 1 is correct. Azure Monitor can unify data from VMs, AKS, and App Service. By integrating them into a single Log Analytics workspace, logs can be centrally queried and retained according to policy. Application Insights (part of Azure Monitor) provides deep insights for web apps, while Container Insights supports AKS. This unified setup aligns with Azure best practices for cross-service monitoring and troubleshooting.
- B. Incorrect.
Option 2 is incorrect. While Azure Diagnostics can be used to collect logs, storing them in separate Storage accounts without a central workspace complicates cross-resource correlation. Additionally, it does not provide built-in capabilities for creating unified queries or dashboards across different types of logs as effectively as a Log Analytics workspace.
- C. Incorrect.
Option 3 is incorrect. Using a different monitoring solution for each resource type can lead to fragmentation. This makes it difficult to consolidate metrics and logs or to efficiently troubleshoot issues that span multiple services. Azure Monitor is specifically designed to integrate across all Azure resources.
- D. Incorrect.
Option 4 is incorrect. Azure Monitor Metrics alone only captures numerical metrics. Without additional log collection or Application Insights for telemetry, you lose valuable diagnostic information. A comprehensive solution requires logs and application-level insights in addition to basic metrics.