Pass Your Microsoft AB-900 Exam Easy!

AI-aware DLP can inspect and control supported content exchanges. It would support sensitive prompt leakage prevention, not the stated traceable sensitive Copilot activity.

AI posture reporting combines supported usage patterns with sensitive data findings. Its purpose is AI adoption-associated data risk context; the specified need is traceable sensitive Copilot activity.

AI grounding respects effective source permissions; oversharing is a source governance fault. Its purpose is prevention of unauthorized AI source discovery; the specified need is traceable sensitive Copilot activity.

Hold requirements prevent loss of evidence despite ordinary deletion schedules. The action is relevant to hold-compliant preservation rather than suspicious worker file-exfiltration investigation.

DLP activity captures the rule and destination context for a violation. This helps with file-sharing policy incident evidence instead of the required suspicious worker file-exfiltration investigation.

Reviewers assess policy context and document their disposition. The action is relevant to conduct violation assessment rather than suspicious worker file-exfiltration investigation.

Document fingerprints match against a reference form structure. It is used for recognition of standard legal forms; this scenario calls for precise matching of known customer IDs.

Content classification reports where structured sensitive data is found. That addresses discovery of structured financial identifiers, whereas the current case requires precise matching of known customer IDs.

Semantic classification can identify document themes beyond fixed patterns. It is used for discovery of unstructured trade secret content; this scenario calls for precise matching of known customer IDs.

RAC adds a site-level group boundary above ordinary link permissions. Its purpose is hard restriction of a high-risk site; the specified need is mandatory preservation of AI interaction data.

Aggregated risk reporting describes activity patterns without changing access. Its purpose is trend monitoring of insider-risk alerts; the specified need is mandatory preservation of AI interaction data.

Sharing reports reveal potentially overshared sites and trends. It would support broad link-exposure risk identification, not the stated mandatory preservation of AI interaction data.

Communication Compliance handles supported workplace conduct messages. This helps with review of harmful employee messages instead of the required insider-driven exfiltration case.

DLP incidents show sensitive data matches and policy enforcement. The action is relevant to investigation of sensitive document transfer rather than insider-driven exfiltration case.

eDiscovery organizes litigation-related content finding and holding. The action is relevant to formal legal evidence collection rather than insider-driven exfiltration case.

Content policy and data-loss alerts address different violation classes. It is used for AI-related communication policy triage; this scenario calls for legally responsive Copilot conversations.

Compliance Manager supports framework-mapped control review and improvements. That addresses assessment of AI-relevant compliance duties, whereas the current case requires legally responsive Copilot conversations.

AI-specific signals can surface use of protected data categories. It is used for classified information used during AI interactions; this scenario calls for legally responsive Copilot conversations.

Compliance Manager organizes compliance-control assessments and improvement tasks. Its purpose is framework evidence and control tracking; the specified need is problematic workplace messages.

Content classification discovery identifies data locations and matched types. It would support locating sensitive identity data, not the stated problematic workplace messages.

Insider risk focuses on configured risky behavior by trusted users. Its purpose is suspected malicious insider activity; the specified need is problematic workplace messages.

Compliance Manager tracks completion and corresponding assessment status. The action is relevant to regulatory readiness progress rather than regulation-specific control assessment.

Improvement actions can track implementation evidence for assessment controls. The action is relevant to documented proof of a compliance control rather than regulation-specific control assessment.

The assessment assigns responsibility for relevant controls. This helps with responsibility partition for assessed controls instead of the required regulation-specific control assessment.

Activity explorer records supported label events and associated actors. That addresses activity behind an actual label downgrade, whereas the current case requires litigation-driven content collection.

AI posture telemetry identifies sensitive-data use in AI applications. It is used for sensitive information in AI prompts; this scenario calls for litigation-driven content collection.

Data classification inventory identifies matching content in covered workloads. It is used for discovery of stored sensitive content; this scenario calls for litigation-driven content collection.

Insider risk correlates configured risky user actions. Its purpose is suspected departing-employee exfiltration; the specified need is auditable disposition of employee-risk alert.

Privacy-aware insider risk limits exposed personal identity data during triage. It would support privacy-protecting investigation, not the stated auditable disposition of employee-risk alert.

Policy tuning reduces known benign matches without disabling relevant risk detection. Its purpose is fewer false-positive user-risk cases; the specified need is auditable disposition of employee-risk alert.

Alert details identify the sensitive type, location and enforcement reason. The action is relevant to evidence for a sensitive outbound email block rather than repeated data-loss incident response.

Simulated matches allow validation before production enforcement. This helps with impact testing of a new DLP rule instead of the required repeated data-loss incident response.

Governed exceptions avoid weakening protection for all users. The action is relevant to narrowly authorized protected-data sharing rather than repeated data-loss incident response.