You have an Azure subscription that contains the virtual machines shown in the following table. From Azure Security Center, you turn on Auto Provisioning. You deploy the virtual machines shown in…

Question

Options

• AVM3 only
• BVM1 and VM3 only
• CVM3 and VM4 only
• DVM1, VM2, VM3, and VM4

• A
  8% (3)
• B
  5% (2)
• C
  15% (6)
• D
  72% (28)

Explanation

Explanation

When Auto Provisioning is enabled in Azure Security Center (now Microsoft Defender for Cloud), it automatically installs the Microsoft Monitoring Agent (MMA) on all virtual machines in the subscription - both existing VMs and any newly deployed VMs - regardless of whether they were created before or after Auto Provisioning was turned on. This means VM1 and VM2 (existing VMs) receive the agent retroactively, and VM3 and VM4 (newly deployed VMs) receive it automatically upon deployment, making D (all four VMs) correct.

Options A, B, and C are incorrect because they suggest the agent is only installed on a subset of VMs - these distractors try to trick you into thinking Auto Provisioning only applies to new VMs, or only to certain operating systems, but the feature applies universally across all VMs in the subscription.

Memory Tip: Think of Auto Provisioning as a "catch-all net" - once you enable it, it casts backward (existing VMs) and forward (future VMs), ensuring no VM is left unmonitored. If it were only for new VMs, it would be called "New VM Provisioning," not Auto Provisioning.

No community discussion yet for this question.