Examkin

Question

Difficulty: Very hardAzure Monitor and Log Analytics

A multinational financial firm is migrating a mission-critical banking application to Azure. The architecture includes Azure App Service, Azure Virtual Machines (VMs) running custom transactional software, and Azure SQL Database. The compliance and security teams require:

1. A mechanism to detect and alert on service-wide outages or scheduled maintenance in Azure regions where their resources reside.
2. A centralized repository to run complex queries, correlate events, and analyze IIS web server access logs and application-level trace logs from the VMs.
3. Near real-time alerting on virtual machine CPU spikes that triggers automated scaling actions.

Which of the following configurations correctly align these Azure services with the firm's requirements? (Select TWO)

  1. Azure Service Health must be utilized to track platform-level events such as regional service outages, planned maintenance, and service advisories, whereas Azure Monitor is used to collect and analyze telemetry data from the firm's specific deployed resources.Answer
  2. B
    Azure Service Health should be configured to aggregate VM guest OS transaction logs and IIS logs so that operations can write Kusto Query Language (KQL) queries to identify application errors.
  3. Azure Monitor Logs (via a Log Analytics workspace) must be configured to ingest and query custom VM application logs using Kusto Query Language (KQL), while Azure Monitor Metrics should be used to trigger auto-scaling based on CPU utilization.Answer
  4. D
    Azure Service Health should be configured to trigger VM auto-scaling based on resource CPU utilization metrics, while Azure Monitor Metrics is used to store and query the application's multi-line trace logs.

Answer

The configuration using Azure Service Health for tracking platform-level issues, Azure Monitor Logs for querying guest OS logs, and Azure Monitor Metrics for CPU metric alerting.
To track regional platform outages and maintenance, the firm must use Azure Service Health, which communicates issues originating from the Azure platform. To analyze guest OS and application-level log events using KQL, the firm must use Azure Monitor Logs (via Log Analytics). To configure near real-time autoscale alerts based on VM CPU utilization, Azure Monitor Metrics must be used since it stores numerical performance data.

Step-by-Step Solution

1
Analyze the requirement for detecting service-wide outages or scheduled maintenance in Azure regions.
Identify that Azure Service Health is the dedicated service for tracking platform-wide issues, regional outages, and planned maintenance affecting Azure infrastructure.
Azure Service Health provides global and regional notifications, whereas Azure Monitor tracks the health and performance of specific resources deployed by the customer.
2
Analyze the requirement for querying, correlating, and analyzing custom application trace logs and IIS web server logs from VMs.
Identify that Azure Monitor Logs (stored in a Log Analytics workspace) aggregates text-based log data and enables querying using Kusto Query Language (KQL).
Azure Monitor Metrics is designed for time-series numerical data, not multi-line text logs, and Azure Service Health does not collect resource-specific log files.
3
Analyze the requirement for near real-time CPU utilization alerts that trigger auto-scaling actions.
Identify that Azure Monitor Metrics captures numerical telemetry (like CPU usage) at high frequency and is integrated with Azure Autoscale to trigger resource scaling.
Azure Monitor Metrics is optimized for quick, lightweight numerical evaluation, making it ideal for immediate scaling triggers, unlike log search queries which have higher latency.
4
Evaluate the choices to select the two options that correctly align these mapping principles.
Select the statement distinguishing Azure Service Health from resource telemetry, and the statement mapping logs to Azure Monitor Logs (KQL) and scaling to Azure Monitor Metrics.
This ensures the correct tools are paired with their corresponding architectural requirements while filtering out options that confuse Azure Monitor with Azure Service Health.

Key Concept

Azure Monitor vs. Azure Service Health, and Azure Monitor Logs vs. Metrics
Estimated Time:3m 0s
Rate this question

Topics

Azure Monitor and Log Analytics

More questions from this topic