A parks and recreation department wants a SharePoint report on data access governance for the permits site collection. What should they run?

A parks and recreation department that wants a SharePoint report on data access governance for the permits site collection should run a data access governance (DAG) report. DAG reports surface sharing and access posture so administrators can see how open a site collection is—Everyone links, broad sharing patterns, and related governance signals—supporting remediation on permits content.

A SharePoint usage analytics report for the permits site only reviews visits and engagement and does not report data access governance or sharing posture. A Microsoft Purview eDiscovery search for the permits site locates responsive content for legal matters and does not report data access governance or sharing posture. A SharePoint site storage metrics report for the permits site reviews quota usage and file trends and does not report data access governance or sharing posture. Each option fails by concept because it is a collaboration or Office feature unrelated to SharePoint DAG reporting.

Exam caveat: DAG reports are SharePoint governance/reporting artifacts for access and sharing posture. They inform remediation and Copilot-readiness reviews but do not themselves apply restricted access control or delete content. AB-900 links “report on data access governance / oversharing patterns” to DAG reports.

Operational check: From the SharePoint admin center, generate or open the DAG report scoped to the permits site collection, review sites or items with excessive sharing, assign owners cleanup tasks, track closure, and re-run the report after changes to confirm the permits site’s access posture improved before wider AI enablement.