Exam Bundle

A least-privileged test account cannot access the newly restricted knowledge content. That evidence would matter for A Copilot agent has broader access than intended because a source site is open to everyone. but the current implementation is Correct source permissions and apply sensitivity labels or DLP before exposing them to AI search. The requirement being evaluated here is: A security team wants to restrict public sharing of files likely to be retrieved by enterprise AI assistants.

The investigation identifies whether protected generated content left the organization serves a different requirement. It does not resolve the specific issue addressed by unauthorized users cannot retrieve the protected source content through the assistant.

Sensitive source files receive the expected label before AI use. That evidence would matter for An AI product team asks for automatic classification of files that Copilot might read. but the current implementation is Correct source permissions and apply sensitivity labels or DLP before exposing them to AI search. The requirement being evaluated here is: A security team wants to restrict public sharing of files likely to be retrieved by enterprise AI assistants.

Configuring supported Purview controls for Microsoft Foundry-connected AI applications addresses a different data-protection mechanism. It does not provide the specific safeguard required here: use the DSPM for AI activity dashboards and appropriate reporting filters.

Reviewing supported Purview AI data security controls for Entra-registered applications addresses a different classification need. It does not demonstrate the trend report covers the expected apps, users and time periods.

Configuring appropriate supported retention and compliance controls for the eligible AI interaction data addresses a different data-protection mechanism. It does not provide the specific safeguard required here: use the DSPM for AI activity dashboards and appropriate reporting filters.

A supported test integration begins supplying expected discovery signals serves a different requirement. It does not resolve the specific issue addressed by the trend report covers the expected apps, users and time periods.

Sensitive source files receive the expected label before AI use. That evidence would matter for An AI product team asks for automatic classification of files that Copilot might read. but the current implementation is Use the DSPM for AI activity dashboards and appropriate reporting filters. The requirement being evaluated here is: An administrator needs a view of AI activity trends over time rather than individual alerts.

The AI risk dashboard identifies relevant connected apps and data exposure signals serves a different requirement. It does not resolve the specific issue addressed by the trend report covers the expected apps, users and time periods.

Using supported AI activity monitoring and applicable data classification controls addresses a different data-protection mechanism. It does not provide the specific safeguard required here: verify application category, connector support, data ingestion and applicable prerequisites.

Configuring and verify supported sensitivity label protection throughout Microsoft 365 workloads addresses a different classification need. It does not demonstrate a supported test integration begins supplying expected discovery signals.

Using the Purview AI application categories and connected app discovery capabilities does not demonstrate the classification result required here: a supported test integration begins supplying expected discovery signals.

Sensitive source files receive the expected label before AI use serves a different requirement. It does not resolve the specific issue addressed by a supported test integration begins supplying expected discovery signals.

The trend report covers the expected apps, users and time periods. That evidence would matter for An administrator needs a view of AI activity trends over time rather than individual alerts. but the current implementation is Verify application category, connector support, data ingestion and applicable prerequisites. The requirement being evaluated here is: A newly added AI service is missing from the data security posture dashboard.

The AI risk dashboard identifies relevant connected apps and data exposure signals serves a different requirement. It does not resolve the specific issue addressed by a supported test integration begins supplying expected discovery signals.

Correct source permissions and apply sensitivity labels or DLP before exposing them to AI search addresses a different classification need. It does not demonstrate a least-privileged test account cannot access the newly restricted knowledge content.

Evaluating the Microsoft Purview-supported protections and workload permissions for Fabric AI experiences does not demonstrate the classification result required here: a least-privileged test account cannot access the newly restricted knowledge content.

Applying least-privilege permissions and supported Microsoft Purview protection policies for connected content addresses a different classification need. It does not demonstrate a least-privileged test account cannot access the newly restricted knowledge content.

A test Copilot interaction does not reveal content beyond the user's authorized access. That evidence would matter for A newly assigned security administrator inherits this open requirement: A Microsoft 365 Copilot rollout must respect document-level sensitivity labels. The team needs a supported control, not only a policy document. but the current implementation is Remediate SharePoint access permissions and evaluate the source data oversharing finding. The requirement being evaluated here is: A Copilot agent has broader access than intended because a source site is open to everyone.

Unauthorized users cannot retrieve the protected source content through the assistant serves a different requirement. It does not resolve the specific issue addressed by a least-privileged test account cannot access the newly restricted knowledge content.

A test interaction honors item access and relevant protection restrictions serves a different requirement. It does not resolve the specific issue addressed by a least-privileged test account cannot access the newly restricted knowledge content.

Using supported AI activity monitoring and applicable data classification controls addresses a different classification need. It does not demonstrate sensitive source files receive the expected label before AI use.

Applying least-privilege permissions and supported Microsoft Purview protection policies for connected content does not demonstrate the classification result required here: sensitive source files receive the expected label before ai use.

Verifying application category, connector support, data ingestion and applicable prerequisites addresses a different data-protection mechanism. It does not provide the specific safeguard required here: implement Microsoft Purview classification and labeling at the underlying content locations.

A supported test integration begins supplying expected discovery signals serves a different requirement. It does not resolve the specific issue addressed by sensitive source files receive the expected label before AI use.

Recorded test activity appears in scoped AI security reports serves a different requirement. It does not resolve the specific issue addressed by sensitive source files receive the expected label before AI use.

The trend report covers the expected apps, users and time periods serves a different requirement. It does not resolve the specific issue addressed by sensitive source files receive the expected label before AI use.

Configuring supported Purview DLP controls for eligible generative AI apps and interactions does not demonstrate the classification result required here: the investigation identifies whether protected generated content left the organization.

Using supported AI activity monitoring and applicable data classification controls addresses a different data-protection mechanism. It does not provide the specific safeguard required here: correlate supported AI audit activity with sharing or DLP events where available.

Using the DSPM for AI activity dashboards and appropriate reporting filters does not demonstrate the classification result required here: the investigation identifies whether protected generated content left the organization.

Unauthorized users cannot retrieve the protected source content through the assistant serves a different requirement. It does not resolve the specific issue addressed by the investigation identifies whether protected generated content left the organization.

The assessment identifies high-risk sites for remediation serves a different requirement. It does not resolve the specific issue addressed by the investigation identifies whether protected generated content left the organization.

The AI risk dashboard identifies relevant connected apps and data exposure signals. That evidence would matter for A division is preparing a scoped Microsoft 365 rollout for this business need: A company wants visibility into which enterprise AI apps access confidential Microsoft 365 content. The pilot must establish a technical control before it can expand. but the current implementation is Correlate supported AI audit activity with sharing or DLP events where available. The requirement being evaluated here is: A risk team wants to review AI-generated content that has been shared externally.