AZ-801 · Question #157
Your on-premises network contains an Active Directory Domain Services (AD DS) domain. The domain contains 10 servers that run Windows Server. You have an Azure subscription. The subscription contains
This question tests knowledge of how to deploy the Azure Monitor Agent (AMA) to both Azure-native VMs and on-premises servers, which require different onboarding mechanisms before agent installation is possible.
Question
Explanation
This question tests knowledge of how to deploy the Azure Monitor Agent (AMA) to both Azure-native VMs and on-premises servers, which require different onboarding mechanisms before agent installation is possible.
Approach. For Azure virtual machines, Azure Policy is the recommended approach - specifically the built-in policy initiatives that deploy the Azure Monitor Agent as a VM extension automatically at scale. For on-premises Windows servers, you must first onboard them using Azure Arc (Azure Arc-enabled servers), which projects on-premises machines into Azure as managed resources; once Arc-enabled, the Azure Monitor Agent can be deployed to them as an extension just like Azure VMs. Azure Arc is the critical prerequisite for any Azure management plane capability - including AMA - to reach non-Azure machines. Data Collection Rules (DCRs) are then associated with the agent to define what telemetry is collected, but DCRs are a configuration concern, not the installation mechanism.
Concept tested. Azure Monitor Agent deployment strategy: Azure Policy for native Azure VMs vs. Azure Arc as the mandatory onboarding gateway for on-premises servers before AMA installation is possible.
Reference. https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-manage
Topics
Community Discussion
No community discussion yet for this question.