A transit authority wants the Microsoft Purview family associated with labeling and protecting sensitive documents. Which choice fits?

A transit authority seeking the Microsoft Purview family associated with labeling and protecting sensitive documents should choose Microsoft Purview Information Protection. That capability family is specifically about classifying content and applying protection such as sensitivity labels and related encryption/rights management behaviors for documents and emails.

Microsoft Purview Data Lifecycle Management governs retention and disposal schedules for content, not the labeling and protection of documents based on sensitivity. Microsoft Purview Insider Risk Management surfaces risky insider activity patterns; it does not apply sensitivity labels or protection to documents. Microsoft Purview Communication Compliance monitors message content for policy violations; it is not the family that labels and protects documents with sensitivity classifications.

Exam caveat: Map “labeling and protecting documents” language to Purview Information Protection. Defender, billing, and distribution groups are common cross-product distractors on AB-900 Purview questions.

Operational check: In Purview, review Information Protection labels used by the transit authority, confirm auto-labeling or recommended labeling where appropriate for sensitive transit documents, test open/deny behaviors for unauthorized users, and document the label taxonomy for operations staff.