Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…

Question

Options

• AYes
• BNo

• A
  6% (2)
• B
  94% (29)

Explanation

Option B (No) is correct because Microsoft Antimalware for Azure is not a Windows feature that can be installed manually through Server Manager or PowerShell's Add-WindowsFeature command - it is an Azure VM Extension that must be deployed through the Azure platform itself.

The correct approach to deploy Microsoft Antimalware to 50 virtual machines at scale would be to use Azure PowerShell, Azure CLI, ARM templates, or Azure Security Center, which can push the IaaSAntimalware extension to multiple VMs simultaneously without requiring individual logins.

Option A (Yes) is wrong because manually connecting to each of 50 virtual machines to add a Windows feature is both the incorrect method and an inefficient, unscalable approach - Microsoft Antimalware is not even available as a native Windows feature in this context.

Memory Tip: Think of Microsoft Antimalware in Azure as an Extension, not a Feature. Features live inside the OS; Extensions are deployed from Azure onto the VM. Whenever a question asks about deploying something to many VMs at once, look for Azure-level tools (PowerShell, ARM templates, Policy) rather than manual, per-machine methods.

No community discussion yet for this question.