Pass Your Microsoft AB-900 Exam Easy!

Sensitive information types match structured patterns and proximity evidence. It would support structured national-identifier detection, not the stated high-confidence match against approved data.

Classifier models identify topic and content patterns not tied to one exact token. Its purpose is semantic R&D sensitive-content detection; the specified need is high-confidence match against approved data.

Document fingerprinting identifies content resembling a supplied exemplar. Its purpose is template-specific document identification; the specified need is high-confidence match against approved data.

AI-specific Purview controls can limit processing of selected classified sources. The action is relevant to sensitive source exclusion from AI processing rather than AI user-action event evidence.

eDiscovery can search supported interaction records for legal response. This helps with discovery of relevant AI conversations instead of the required AI user-action event evidence.

Supported retention policies govern preservation and expiration of interaction records. The action is relevant to regular retention of AI communications rather than AI user-action event evidence.

Recorded changes support disposition accountability. It is used for auditable record label changes; this scenario calls for mandatory legal evidence preservation.

Disposition review governs human approval before permanent deletion. That addresses reviewed record disposal, whereas the current case requires mandatory legal evidence preservation.

Retention preserves records for the prescribed period before deletion. It is used for deletion following mandatory preservation; this scenario calls for mandatory legal evidence preservation.

Rights management can constrain permitted operations independent of file retrieval. Its purpose is limited document use after access; the specified need is policy-blocked sensitive outbound mail.

Retention and sensitivity serve separate lifecycle and confidentiality purposes. Its purpose is independent retention and confidentiality classification; the specified need is policy-blocked sensitive outbound mail.

File-level encryption can enforce authorized use beyond the SharePoint site boundary. It would support persistent protection on a shared document, not the stated policy-blocked sensitive outbound mail.

Compliance Manager ties controls and improvement actions to compliance frameworks. This helps with framework-based compliance evidence instead of the required location of classified content.

Security score recommendations emphasize security posture rather than audit controls. The action is relevant to security control implementation priorities rather than location of classified content.

AI posture reporting focuses risks from generative AI usage and content exposure. The action is relevant to AI interaction and oversharing risk visibility rather than location of classified content.

Label policies expose approved classification choices to eligible users. It is used for staff selection of approved document labels; this scenario calls for accountable reduction of file sensitivity.

Coverage reporting identifies labeled versus unlabeled content. That addresses visibility into missing document classification, whereas the current case requires accountable reduction of file sensitivity.

Sensitivity labels can classify and protect files using scoped encryption settings. That addresses classified encrypted finance workbook, whereas the current case requires accountable reduction of file sensitivity.

Sensitive information types detect structured patterns and corroborating evidence. It would support detection of structured payment card data, not the stated matching known sensitive identifiers.

Trainable classifiers identify content by learned characteristics beyond fixed regular expressions. Its purpose is unstructured proprietary subject classification; the specified need is matching known sensitive identifiers.

Fingerprints match document structures against an approved exemplar. It would support classification of a known document form, not the stated matching known sensitive identifiers.

Exchange DLP evaluates matching content during mail transport and applies configured actions. This helps with sensitive outbound mail control instead of the required sensitive data in team conversations.

Cloud file DLP can detect sensitive content and restrict sharing actions where supported. The action is relevant to classified cloud-file sharing enforcement rather than sensitive data in team conversations.

Endpoint DLP controls supported device actions against protected content. This helps with local removable-media exfiltration control instead of the required sensitive data in team conversations.

Rule precedence and effective actions determine observed protection behavior. That addresses diagnosis of conflicting DLP outcomes, whereas the current case requires actionable sensitive-data incident triage.

Policy tips make controls visible while approved overrides can be recorded. That addresses guided exception to a DLP rule, whereas the current case requires actionable sensitive-data incident triage.

Test mode measures candidate matches without necessarily enforcing blocks. It is used for safe predeployment DLP evaluation; this scenario calls for actionable sensitive-data incident triage.

Retention labels classify items into lifecycle rules independently of location-wide policies. Its purpose is item-level contract retention; the specified need is scheduled preservation followed by disposal.

Record declaration adds governed protections and disposition handling. It would support protected declared business record, not the stated scheduled preservation followed by disposal.

Retention policies apply broad retention behavior to supported workloads. It would support location-wide mail retention, not the stated scheduled preservation followed by disposal.

Retention wins over deletion while legally required preservation is active. This helps with conflict-safe content preservation instead of the required evidence of record lifecycle assignment.

Holds preserve covered data against ordinary deletion during legal matters. The action is relevant to litigation-driven content preservation rather than evidence of record lifecycle assignment.

Disposition review provides accountable approval before managed record destruction. This helps with controlled final deletion of records instead of the required evidence of record lifecycle assignment.