A parks department analyst asks whether Microsoft Purview is the tool that deploys new virtual machines for seasonal staff. What should the trainer explain?
Select an answer to reveal the explanation.
Short Explanation
Purview does not spin up VMs for the summer lifeguard app. It helps you understand and govern data. Compute deployment stays with portal, CLI, ARM, and friends—not the data catalog.
Full Explanation
Microsoft Purview helps organizations understand and govern data through cataloging, classification themes, and compliance visibility across municipal datasets. It is not a compute deployment service and does not provision virtual machines for seasonal parks staff. Trainers should separate the data-governance lane from the Azure portal, Azure CLI, PowerShell, ARM/Bicep templates, and related tools that actually create and configure VMs for seasonal workloads.
Purview does not deploy VMs or automatically assign RBAC roles as its core purpose. Purview is not a content delivery network that caches VM images near citizens. Purview is also not a prerequisite that must exist before any Azure VM can start in a region—compute can run without a data catalog, though a mature governance program may still want catalog coverage of the data those VMs process.
Exam caveat: questions often tempt you to overload familiar product names onto every task; match Purview only to data understanding and governance scenarios, not to every Azure verb in the stem. Operational check: create or review a seasonal VM deployment runbook that lists portal, CLI, or infrastructure-as-code steps plus RBAC owners, and explicitly note that Purview is consulted for datasets the seasonal app uses—not as the control that spins up the virtual machine.