A city privacy team needs tooling to assess personal-data handling risks and subject-rights style workflows in Microsoft 365. Which solution should they identify?
Select an answer to reveal the explanation.
Short Explanation
Privacy risk and subject-rights work lands on Microsoft Priva—not Bookings branding or Windows rings. Priva is the privacy-focused Microsoft 365 tooling named on the skills list.
Full Explanation
Microsoft Priva is the Microsoft 365 privacy solution aimed at assessing personal-data handling risks and supporting subject-rights style workflows. When a city privacy team needs that tooling, Priva is the skills-list answer—distinct from booking, deployment, or automation-count distractors that sound operational but do not govern privacy risk.
Microsoft Bookings page branding only affects appointment scheduling appearance. Windows deployment rings alone control update rollout rings, not privacy risk assessments. Power Automate connector counts alone measure automation connectivity, not privacy governance over personal data stored in Microsoft 365.
Exam caveat: Priva addresses privacy risk and rights; Purview eDiscovery addresses legal content discovery—do not swap those labels in privacy-office versus lawsuit scenarios. Operational check: identify overexposed personal data insights in Priva for a pilot department, walk through a subject-rights request workflow with privacy officers, and confirm role permissions limit who can access citizen personal-data findings. For municipal MS-900 scenarios, keep the product-to-purpose mapping explicit so distractors about unrelated UX, networking, or licensing features do not displace the correct compliance or security control.