Pass Your Microsoft AB-900 Exam Easy!

Sensitive information types detect structured patterns and corroborating evidence. It would support detection of structured payment card data, not the stated unstructured proprietary subject classification.

Fingerprints match document structures against an approved exemplar. It would support classification of a known document form, not the stated unstructured proprietary subject classification.

Exact data match uses hashed reference values for high-confidence sensitive data discovery. Its purpose is matching known sensitive identifiers; the specified need is unstructured proprietary subject classification.

Teams DLP evaluates supported messaging content against sensitive data rules. The action is relevant to sensitive data in team conversations rather than classified cloud-file sharing enforcement.

Exchange DLP evaluates matching content during mail transport and applies configured actions. This helps with sensitive outbound mail control instead of the required classified cloud-file sharing enforcement.

Endpoint DLP controls supported device actions against protected content. This helps with local removable-media exfiltration control instead of the required classified cloud-file sharing enforcement.

Rule precedence and effective actions determine observed protection behavior. That addresses diagnosis of conflicting DLP outcomes, whereas the current case requires safe predeployment DLP evaluation.

DLP alerts provide matched-rule context for investigation and follow-up. It is used for actionable sensitive-data incident triage; this scenario calls for safe predeployment DLP evaluation.

Policy tips make controls visible while approved overrides can be recorded. That addresses guided exception to a DLP rule, whereas the current case requires safe predeployment DLP evaluation.

Record declaration adds governed protections and disposition handling. It would support protected declared business record, not the stated item-level contract 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 item-level contract retention.

Retention policies apply broad retention behavior to supported workloads. It would support location-wide mail retention, not the stated item-level contract retention.

Retention wins over deletion while legally required preservation is active. This helps with conflict-safe content preservation instead of the required litigation-driven content preservation.

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

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

Case workflows preserve the investigation outcome and reasoning. It is used for accountable insider-risk case closure; this scenario calls for privacy-aware insider-risk review.

Insider risk combines configured indicators to identify risky internal behavior. That addresses investigation of concerning employee data activity, whereas the current case requires privacy-aware insider-risk review.

Indicator policies help detect defined risky employee activity patterns. That addresses policy for suspicious user exfiltration, whereas the current case requires privacy-aware insider-risk review.

Better conditions reduce irrelevant flagging while retaining risk signals. It would support tuned misconduct detection quality, not the stated restricted sensitive-message review.

Review workflows provide auditable case handling for flagged messages. Its purpose is documented response to harmful communication; the specified need is restricted sensitive-message review.

Communication Compliance monitors supported communications for conduct and policy violations. It would support workplace communication policy review, not the stated restricted sensitive-message review.

DSPM assessments highlight sensitive-data exposure patterns relevant to AI usage. This helps with Copilot-focused oversharing risk assessment instead of the required specific AI interaction activity evidence.

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 specific AI interaction activity evidence.

DSPM for AI surfaces AI activity, exposure indicators, and recommended controls. This helps with organization-wide AI data-security visibility instead of the required specific AI interaction activity evidence.

Content labels classify individual documents and may protect the file. That addresses file-level confidentiality, whereas the current case requires site-level classification policy.

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

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

DLP telemetry records policy match and enforcement. Its purpose is source of a sensitive mail protection action; the specified need is litigation search across supported content.

Audit records document supported user and administrative operations. It would support file deletion activity evidence, not the stated litigation search across supported content.

Holds preserve relevant items during a legal matter. It would support preservation of responsive mailbox data, not the stated litigation search across supported content.

Insider Risk cases include relevant configured behavioral risk signals. This helps with employee behavioral risk investigation instead of the required action-centered sensitive-data event history.

eDiscovery search targets responsive content for legal review. The action is relevant to search and collect case-specific email evidence rather than action-centered sensitive-data event history.

Content explorer summarizes classified content across supported locations. This helps with inventory of content matching a sensitive type instead of the required action-centered sensitive-data event history.