A city diagram needs a one-line definition of Azure Resource Manager for new staff. Which statement is accurate?
Select an answer to reveal the explanation.
Short Explanation
ARM is Azure’s backstage crew for deploy-and-manage. Portal clicks, CLI, and templates all talk through that management fabric. It is not wallpaper for the portal or a CDN edge.
Full Explanation
Azure Resource Manager (ARM) is the deployment and management service for Azure resources. Portal actions, Azure CLI, Azure PowerShell, and templates ultimately work through this management fabric to create, update, organize (for example via resource groups), and control access patterns for resources in a subscription. For new staff, that one-line definition separates “pretty UI” from “the control plane service underneath.”
Calling ARM only a desktop theme pack for the portal confuses presentation with the management service. Describing ARM as a classic ASM-only API that ignores resource groups points at the older classic model rather than modern Azure Resource Manager organization. Calling ARM a consumer CDN endpoint unrelated to deployments invents a delivery-network identity for a control-plane service.
Exam caveat: people colloquially say “ARM templates” for JSON definitions, but Azure Resource Manager itself is the broader deployment and management service those templates target. Operational check: create a resource via portal and via a simple template or CLI in the same subscription, then show both results living in resource groups managed through the same Resource Manager model (activity log / deployment history as available).