You have an Azure subscription that contains multiple virtual machines. The virtual machines host an SAP non-production landscape on Azure. You need to configure the virtual machines to stop and…

Question

Options

• Aan Azure Monitor workbook
• Ban Azure Resource Manager (ARM) template
• Ca virtual machine scale set
• Dan Azure Automation account

• A
  2% (1)
• B
  5% (2)
• D
  93% (41)

Explanation

Azure Automation Account is the right tool because it provides native scheduling capabilities through runbooks and schedules, allowing you to automate start/stop operations across multiple VMs at defined times - all from a single, centrally managed service with minimal ongoing effort.

Why the distractors are wrong:

• A (Azure Monitor Workbook): Workbooks are visualization and reporting tools for monitoring data; they have no ability to execute actions or control VM state.
• B (ARM Template): Templates define and deploy infrastructure declaratively but don't provide scheduling - you'd still need another mechanism to trigger them repeatedly.
• C (VM Scale Set): Scale sets enable autoscaling based on load or metrics, but they manage instance count dynamically, not scheduled start/stop of existing VMs.

Memory tip: Think of Azure Automation as your "IT operations robot" - it runs scripts on a schedule so you don't have to. For SAP non-prod environments where cost savings via scheduled shutdowns matter, Automation Account + a PowerShell runbook is the standard pattern. If you see "schedule," "automate," or "minimize effort" for VM lifecycle tasks, Automation Account is almost always the answer.

No community discussion yet for this question.