A county wants Azure Policy–style governance themes applied to servers that still run in its datacenter. Which Azure approach describes that goal at fundamentals depth?
Select an answer to reveal the explanation.
Short Explanation
Want Azure’s governance habits on metal that still lives downtown? Arc is how those outside servers show up for Azure management themes. Renaming a building East US does not enroll anything.
Full Explanation
An Azure Arc–enabled approach describes bringing outside servers under Azure management and governance so Policy-style governance themes—and related control plane consistency—can extend to machines that still run in the county datacenter. Fundamentals framing is the goal of hybrid visibility and control, not a deep implementation lab of every agent setting.
Moving every server into Azure Blob Archive so Policy applies to cold bytes misunderstands both storage tiers and governance: Archive is for rarely accessed blob data, not a host enrollment mechanism. Renaming the datacenter to East US 3 without connecting management components changes labels, not control plane membership. Using only the Pricing Calculator cannot enforce configuration standards on hosts; cost estimation is not policy enforcement.
Exam caveat: governance coverage depends on successful onboarding and the specific Arc capabilities in scope—saying “Arc” does not automatically apply every Azure Policy effect without setup. Operational check: pick a pilot on-prem server, onboard it via Arc for the intended resource type, assign a simple audit policy or inventory view, and verify the server appears in Azure management views before expanding.