Exam Bundle

A test interaction honors item access and relevant protection restrictions serves a different requirement. It does not resolve the specific issue addressed by a qualifying test interaction is retained under the relevant policy scope.

The policy detects qualifying test AI interactions and records the effective response. That evidence would matter for A newly assigned security administrator inherits this open requirement: A business wants to configure an AI-focused data loss prevention policy from the Purview experience. The team needs a supported control, not only a policy document. but the current implementation is Configure appropriate supported retention and compliance controls for the eligible AI interaction data. The requirement being evaluated here is: A legal group must retain relevant Copilot prompts and responses where supported.

The investigator finds relevant recorded AI interactions within the authorized scope serves a different requirement. It does not resolve the specific issue addressed by a qualifying test interaction is retained under the relevant policy scope.

Using supported data security AI activity monitoring and DLP activity evidence addresses a different data-protection mechanism. It does not provide the specific safeguard required here: configure appropriate supported retention and compliance controls for the eligible AI interaction data.

Using the Microsoft Purview data security posture management for AI experience for discovery and assessment addresses a different classification need. It does not demonstrate a qualifying test interaction is retained under the relevant policy scope.

Using the DSPM for AI activity dashboards and appropriate reporting filters does not demonstrate the classification result required here: a qualifying test interaction is retained under the relevant policy scope.

A test interaction honors item access and relevant protection restrictions serves a different requirement. It does not resolve the specific issue addressed by a qualifying test interaction is retained under the relevant policy scope.

The policy detects qualifying test AI interactions and records the effective response. That evidence would matter for A newly assigned security administrator inherits this open requirement: A business wants to configure an AI-focused data loss prevention policy from the Purview experience. The team needs a supported control, not only a policy document. but the current implementation is Configure appropriate supported retention and compliance controls for the eligible AI interaction data. The requirement being evaluated here is: A second Microsoft 365 business unit reports the following protection gap: A legal group must retain relevant Copilot prompts and responses where supported. It needs a configuration that can be tested without a tenant-wide change.

The investigator finds relevant recorded AI interactions within the authorized scope serves a different requirement. It does not resolve the specific issue addressed by a qualifying test interaction is retained under the relevant policy scope.

Correct source permissions and apply sensitivity labels or DLP before exposing them to AI search addresses a different classification need. It does not demonstrate the investigator finds relevant recorded AI interactions within the authorized scope.

Configuring supported Purview controls for Microsoft Foundry-connected AI applications does not demonstrate the classification result required here: the investigator finds relevant recorded ai interactions within the authorized scope.

Assigning appropriate Purview DSPM for AI roles using least privilege addresses a different classification need. It does not demonstrate the investigator finds relevant recorded AI interactions within the authorized scope.

Pilot interactions surface in relevant AI activity and risk reporting views. That evidence would matter for A security controls assessment returns an unmet item: A developer team uses Microsoft Foundry and wants data security monitoring around AI interactions. A reviewer asks for the most direct supported remediation in the relevant Purview workload. but the current implementation is Use supported Microsoft Purview Audit or eDiscovery capabilities for eligible AI activity. The requirement being evaluated here is: An audit team wants to search AI interaction activity during an investigation.

The policy detects qualifying test AI interactions and records the effective response serves a different requirement. It does not resolve the specific issue addressed by the investigator finds relevant recorded AI interactions within the authorized scope.

A qualifying test interaction is retained under the relevant policy scope serves a different requirement. It does not resolve the specific issue addressed by the investigator finds relevant recorded AI interactions within the authorized scope.

Correct source permissions and apply sensitivity labels or DLP before exposing them to AI search addresses a different classification need. It does not demonstrate the investigator finds relevant recorded AI interactions within the authorized scope.

Configuring supported Purview controls for Microsoft Foundry-connected AI applications does not demonstrate the classification result required here: the investigator finds relevant recorded ai interactions within the authorized scope.

Assigning appropriate Purview DSPM for AI roles using least privilege addresses a different data-protection mechanism. It does not provide the specific safeguard required here: use supported Microsoft Purview Audit or eDiscovery capabilities for eligible AI activity.

Pilot interactions surface in relevant AI activity and risk reporting views serves a different requirement. It does not resolve the specific issue addressed by the investigator finds relevant recorded AI interactions within the authorized scope.

The policy detects qualifying test AI interactions and records the effective response serves a different requirement. It does not resolve the specific issue addressed by the investigator finds relevant recorded AI interactions within the authorized scope.

A qualifying test interaction is retained under the relevant policy scope serves a different requirement. It does not resolve the specific issue addressed by the investigator finds relevant recorded AI interactions within the authorized scope.

Using DSPM for AI recommendations and risk insights to rank oversharing exposure does not demonstrate the classification result required here: the relevant high-risk ai activity is correlated into an eligible investigation.

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: integrate supported Insider Risk Management and Adaptive Protection signals for AI data security.

Using supported data security AI activity monitoring and DLP activity evidence does not demonstrate the classification result required here: the relevant high-risk ai activity is correlated into an eligible investigation.

The registered AI app is discovered and applicable protection signals are available serves a different requirement. It does not resolve the specific issue addressed by the relevant high-risk AI activity is correlated into an eligible investigation.

A sampled interaction provides visibility into the sensitive content exposure risk serves a different requirement. It does not resolve the specific issue addressed by the relevant high-risk AI activity is correlated into an eligible investigation.

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 Integrate supported Insider Risk Management and Adaptive Protection signals for AI data security. The requirement being evaluated here is: An organization wants to detect high-risk AI use by employees already subject to insider risk review.

Evaluating the Microsoft Purview-supported protections and workload permissions for Fabric AI experiences does not demonstrate the classification result required here: unauthorized users cannot retrieve the protected source content through the assistant.

Using supported data security AI activity monitoring and DLP activity evidence addresses a different data-protection mechanism. It does not provide the specific safeguard required here: correct source permissions and apply sensitivity labels or DLP before exposing them to AI search.

Applying least-privilege permissions and supported Microsoft Purview protection policies for connected content addresses a different classification need. It does not demonstrate unauthorized users cannot retrieve the protected source content through the assistant.

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.