Pass Your Microsoft AB-900 Exam Easy!

Directory membership can trigger license assignment and removal. The action is relevant to lifecycle-based license provisioning rather than accurate temporary privilege state.

Named locations provide reusable network context for sign-in conditions. This helps with trusted office network classification instead of the required accurate temporary privilege state.

Authentication method policy governs permitted method populations. The action is relevant to targeted stronger authentication enrollment rather than accurate temporary privilege state.

Label policies expose approved classification choices to eligible users. It is used for staff selection of approved document labels; this scenario calls for classified encrypted finance workbook.

Coverage reporting identifies labeled versus unlabeled content. That addresses visibility into missing document classification, whereas the current case requires classified encrypted finance workbook.

Label-policy settings can require users to justify classification reductions. It is used for accountable reduction of file sensitivity; this scenario calls for classified encrypted finance workbook.

Trainable classifiers identify content by learned characteristics beyond fixed regular expressions. Its purpose is unstructured proprietary subject classification; the specified need is detection of structured payment card data.

Fingerprints match document structures against an approved exemplar. It would support classification of a known document form, not the stated detection of structured payment card data.

Exact data match uses hashed reference values for high-confidence sensitive data discovery. Its purpose is matching known sensitive identifiers; the specified need is detection of structured payment card data.

Teams DLP evaluates supported messaging content against sensitive data rules. The action is relevant to sensitive data in team conversations rather than sensitive outbound mail control.

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 outbound mail control.

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

Rule precedence and effective actions determine observed protection behavior. That addresses diagnosis of conflicting DLP outcomes, whereas the current case requires guided exception to a DLP rule.

DLP alerts provide matched-rule context for investigation and follow-up. It is used for actionable sensitive-data incident triage; this scenario calls for guided exception to a DLP rule.

Test mode measures candidate matches without necessarily enforcing blocks. It is used for safe predeployment DLP evaluation; this scenario calls for guided exception to a DLP rule.

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

Record declaration adds governed protections and disposition handling. It would support protected declared business record, not the stated location-wide mail retention.

Retain-then-delete keeps content for a minimum period and disposes afterward. Its purpose is scheduled preservation followed by disposal; the specified need is location-wide mail retention.

Holds preserve covered data against ordinary deletion during legal matters. The action is relevant to litigation-driven content preservation rather than conflict-safe content preservation.

Disposition review provides accountable approval before managed record destruction. This helps with controlled final deletion of records instead of the required conflict-safe content preservation.

Lifecycle metadata and audit trail explain governance state. The action is relevant to evidence of record lifecycle assignment rather than conflict-safe content preservation.

Case workflows preserve the investigation outcome and reasoning. It is used for accountable insider-risk case closure; this scenario calls for investigation of concerning employee data activity.

Insider risk privacy controls limit identity visibility until justified. It is used for privacy-aware insider-risk review; this scenario calls for investigation of concerning employee data activity.

Indicator policies help detect defined risky employee activity patterns. That addresses policy for suspicious user exfiltration, whereas the current case requires investigation of concerning employee data activity.

Better conditions reduce irrelevant flagging while retaining risk signals. It would support tuned misconduct detection quality, not the stated workplace communication policy review.

Review workflows provide auditable case handling for flagged messages. Its purpose is documented response to harmful communication; the specified need is workplace communication policy review.

Reviewer roles control visibility of flagged communications. Its purpose is restricted sensitive-message review; the specified need is workplace communication policy review.

AI activity records expose supported interaction metadata and DLP events. The action is relevant to specific AI interaction activity evidence rather than organization-wide AI data-security visibility.

DSPM assessments highlight sensitive-data exposure patterns relevant to AI usage. This helps with Copilot-focused oversharing risk assessment instead of the required organization-wide AI data-security visibility.

Supported Purview protections can restrict handling of labeled sensitive data by Copilot. The action is relevant to policy-governed processing of labeled files rather than organization-wide AI data-security visibility.

Container labels govern supported site and group configuration settings. It is used for site-level classification policy; this scenario calls for file-level confidentiality.

Default labeling provides a starting classification for eligible new files. That addresses baseline classification of new files, whereas the current case requires file-level confidentiality.

Publishing configuration controls available labels and user presentation. It is used for published label catalog for users; this scenario calls for file-level confidentiality.