Implement and manage data classification
9 practice questions under this official exam objective (SC-401), each with the answer key, an option-by-option explanation and instant feedback.
Questions under this objective
9 total · page 1 of 1Which Purview Policies Can Use Fingerprint vs Regex SITs?
This hotspot tests which Microsoft Purview policy types can consume document-fingerprint versus regex sensitive information types. It establishes SIT1
Which Purview Classification Type Fits Employment, Offensive Language, and Medical Emails?
This SC-401 drag-and-drop item asks you to map Exchange Online email conditions—employment offers, offensive language, and medical terms—to Microsoft
How Many Sensitive Info Types Are Needed for SharePoint Watermarks?
This SC-401 scenario asks for the minimum number of sensitive info types needed for SharePoint watermarking and credit-card retention. The answer is t
Enabling Custom Trainable Classifiers with Least Privilege
Learn how to enable custom trainable classifiers in Microsoft Purview for SC-401. The correct first step is starting the opt-in process as a Global Ad
Microsoft Purview Auto-Labeling Policy Scope and Content Matching Logic
Determine which files receive retention labels based on Microsoft Purview auto-labeling policies. Correctly apply location filters and logical operato
Which primary and secondary elements define the employee ID sensitive info type?
A custom Microsoft Purview sensitive information type uses a primary element for the main pattern and supporting elements for corroborating evidence.
How Do You Build a Regex SIT for pjt123456sct Project Codes?
A Microsoft Purview custom sensitive information type for project code pjt123456sct must use a regular expression that matches the literal pjt prefix,
Which Purview SITs Can Be Copied or Edited Directly?
This SC-401 hotspot tests Microsoft Purview sensitive information type behavior: which listed SITs can be copied to create a new SIT, and which can be
How Should You Configure a Regex for SC-401 Project Codes?
Creating a custom sensitive information type for project codes requires a regex that matches exactly three alphabetic characters followed by exactly t