SC-401 · Domain 1: Implement information protection · 34% of the exam
Task 1.2: Implement and manage sensitivity labels in Microsoft Purview
Roles for label administration, labels for items and containers, encryption and content marking, publishing and auto-labeling policies, labels for Teams, groups, SharePoint sites and Power BI, and labeling through Defender for Cloud Apps.
Study it
Sensitivity labels for items and containers, and who administers them
Lesson coming
Encryption and content marking in sensitivity labels
Label publishing policies and auto-labeling policies
Lesson coming
Labels for Teams, groups, SharePoint sites, Power BI and Defender for Cloud Apps
Lesson coming
Sample questions
Try each one before opening the answer. Every option is explained, with the Microsoft documentation page that proves it.
Question 1 · choose 1
A consultant must create and edit sensitivity labels and sensitivity label policies for three months. She must get no permissions for DLP, classifiers or the activity and content explorers. What should you assign?
AThe Information Protection role group, which covers labels and label policies
BThe Compliance Data Administrator role group
CThe Information Protection Readers role group
DA custom role group that holds the Sensitivity Label Administrator role
Show the answer and why
AThe Information Protection role group, which covers labels and label policies
Incorrect
This role group gives full control over all information protection features, including DLP, classifiers and the explorers.
BThe Compliance Data Administrator role group
Incorrect
This role group is one of the options for labels but covers far more than labels.
CThe Information Protection Readers role group
Incorrect
A readers role group can't create or edit labels and policies.
DA custom role group that holds the Sensitivity Label Administrator role
Correct
A custom role group with this role grants label and label policy management without the broader role groups.
Label admins can use the Information Protection role groups, Compliance Data Administrator, Compliance Administrator or Security Administrator, but the Information Protection role group gives full control over all information protection features, including DLP, classifiers and the explorers. For only labels and their policies, create a role group with the Sensitivity Label Administrator role; Sensitivity Label Reader is the read-only role.
Your tenant still uses parent labels. The parent label Confidential applies a header and is published in its own label policy so users can select it on its own; its sublabels are in another policy. You migrate to the modern label scheme. What happens to Confidential?
AA sublabel named Confidential with the same GUID and settings, plus a new label group
BIt becomes a label group that keeps the header setting and passes it to every sublabel
CIt becomes a label group, and items labeled Confidential lose their label
DIt becomes a label group, and you can roll back the migration if users miss it
Show the answer and why
AA sublabel named Confidential with the same GUID and settings, plus a new label group
Correct
A parent label with label actions or its own publishing policy becomes a sublabel with the same name, GUID and settings, plus a label group.
BIt becomes a label group that keeps the header setting and passes it to every sublabel
Incorrect
Label groups support only a name, description, color and priority.
CIt becomes a label group, and items labeled Confidential lose their label
Incorrect
The new sublabel inherits the parent label's GUID, so labeled items keep a valid label.
DIt becomes a label group, and you can roll back the migration if users miss it
Incorrect
Label migration is irreversible.
Label groups replace parent labels and support only name, description, color and priority. A parent label that has label actions such as content marking, or is published in a different policy from its sublabels, is migrated to a sublabel with the same name, label GUID and settings, in addition to a new label group with a new GUID. The migration can't be reversed.
The Board label applies no encryption and a watermark with the text Confidential ${User.PrincipalName}. Board members see the address of the person who labeled each file, not their own. Every page must show the address of whoever opens the file, and readers mustn't be able to remove it. What should you configure?
AChange the watermark text to use ${User.Name}
BAdd the same text as a header and a footer as well as a watermark
CTurn on dynamic watermarks for the label and keep it without encryption
DConfigure encryption for the label and turn on its dynamic watermark
Show the answer and why
AChange the watermark text to use ${User.Name}
Incorrect
Content marking variables insert values of the user who applies the label, and users can edit or remove the marking.
BAdd the same text as a header and a footer as well as a watermark
Incorrect
Standard content markings use the labeling user's values and can be removed by users.
CTurn on dynamic watermarks for the label and keep it without encryption
Incorrect
Dynamic watermarks can only be applied with labels that apply encryption.
DConfigure encryption for the label and turn on its dynamic watermark
Correct
A dynamic watermark shows the address of the user opening the file and can't be removed without removing the label.
A content marking with a variable uses the details of the user who applies the label, and users can change or remove standard markings. A dynamic watermark displays the UPN of the user who's opening the document, can't be changed or removed without removing the label, and is an encryption setting, so it's supported only for labels that apply encryption.
Raj is included in three sensitivity label policies, each with a default label for documents: All Users (order 0) uses General, Finance (order 1) uses Confidential, and Project Atlas (order 2) uses Public. The labels' own priority runs Public, General, Confidential from lowest to highest. Which default label does a new document that Raj creates get?
AGeneral, from the policy that every user has
BPublic, from Project Atlas
CConfidential, the most restrictive of the three defaults
DNo default label, because the three policies conflict
Show the answer and why
AGeneral, from the policy that every user has
Incorrect
The policy with the lowest order number has the lowest priority, so its conflicting settings lose.
BPublic, from Project Atlas
Correct
When policy settings conflict, the setting from the policy with the highest order number is applied.
CConfidential, the most restrictive of the three defaults
Incorrect
Conflicts between label policies are decided by policy order, not by which label is more restrictive.
DNo default label, because the three policies conflict
Incorrect
A conflict doesn't cancel the setting; the highest-priority policy's setting applies.
A user included in several label policies gets the labels and settings from all of them. If settings conflict, such as the default label for documents, the setting from the policy with the highest priority, which is the highest order number, is applied, whatever the priority of the labels themselves.
Labels by priority: Public (0), General (1), Confidential (2), Highly Confidential (3). The Deals library has the default sensitivity label Confidential. A service-side auto-labeling policy for SharePoint applies Highly Confidential to files with credit card numbers and uses its default settings. Mia opens a new document, applies General herself, adds card numbers and uploads it to Deals. Which label does the file end with?
AConfidential, from the library's default label
BHighly Confidential, from the auto-labeling policy
CGeneral, the label Mia applied
DHighly Confidential, after the library first replaces General with Confidential
Show the answer and why
AConfidential, from the library's default label
Incorrect
A library default label doesn't override a label that was applied manually.
BHighly Confidential, from the auto-labeling policy
Incorrect
By default, auto-labeling doesn't replace a manually applied label, even one of lower priority.
CGeneral, the label Mia applied
Correct
Neither the library default label nor the auto-labeling policy, by default, replaces a manually applied label.
DHighly Confidential, after the library first replaces General with Confidential
Incorrect
The library default doesn't replace a manual label, and the policy doesn't replace one by default.
A default label for a document library overrides a lower-priority label unless that label was manually applied. A service-side auto-labeling policy replaces lower-priority labels that were applied automatically, but not a manually applied label unless you select the setting to override manually applied labels of lower priority. Mia's General label therefore stays.
The Labels page lists, top to bottom: Public, General, Confidential (label group with All Employees, then Finance), Highly Confidential. Sites and files use the same labels. Which upload makes SharePoint send the uploader and the site owners an email about the labels?
AA file labeled Highly Confidential uploaded to a site labeled Confidential\Finance
BA file labeled General uploaded to a site labeled Confidential\All Employees
CA file labeled Confidential\All Employees uploaded to a site labeled Confidential\Finance
DAn unlabeled file uploaded to a site labeled Highly Confidential
Show the answer and why
AA file labeled Highly Confidential uploaded to a site labeled Confidential\Finance
Correct
The file's label has a higher priority than the site's label, so the upload is allowed but an email and an audit event are generated.
BA file labeled General uploaded to a site labeled Confidential\All Employees
Incorrect
A file whose label has a lower priority than the site's label isn't a concern; no email or audit event is generated.
CA file labeled Confidential\All Employees uploaded to a site labeled Confidential\Finance
Incorrect
All Employees sits above Finance, so it has the lower priority; no email is generated.
DAn unlabeled file uploaded to a site labeled Highly Confidential
Incorrect
Only a file whose label outranks the site's label generates the email.
The order of the Labels page sets priority: the higher a label sits, the lower its priority, and the most restrictive label belongs at the bottom. When a document with a higher-priority label than the site's label is uploaded, the upload isn't blocked, but SharePoint emails the uploader and the site owners and admins and logs a Detected document sensitivity mismatch audit event. No email is sent for a lower-priority document label.
The Internal label has no encryption setting selected (Control access isn't configured). Theo applies Internal to each item below. Which two items stay encrypted? (Choose TWO.)
AA document he protected himself with Restricted Access in Word
BA file encrypted by a mail flow rule with a rights management template, on which he has Export
CA document labeled Confidential with administrator-defined permissions, on which he has Full Control
DAn email that he encrypted himself with permissions he chose in Outlook
EA Confidential document a colleague sent him, on which he has only View and Edit
Show the answer and why
AA document he protected himself with Restricted Access in Word
Incorrect
Encryption that a user specified is removed when a label without encryption is applied.
BA file encrypted by a mail flow rule with a rights management template, on which he has Export
Correct
Encryption from a rights management template applied without a label is preserved when the label doesn't configure encryption.
CA document labeled Confidential with administrator-defined permissions, on which he has Full Control
Incorrect
Encryption from a label with administrator-defined permissions is removed when the new label doesn't configure encryption.
DAn email that he encrypted himself with permissions he chose in Outlook
Incorrect
Permissions a user specified are removed when the label doesn't configure encryption.
EA Confidential document a colleague sent him, on which he has only View and Edit
Correct
Without the Export or Full Control usage right, or a Rights Management issuer or owner role, he can't apply the label, so the encryption stays.
When a label that doesn't select encryption is applied, encryption that a user specified and encryption from a label with administrator-defined permissions are removed, while encryption from a rights management template is preserved. Removing or replacing encryption also requires the Export or Full Control usage right, or a role such as Rights Management issuer or owner; otherwise the label can't be applied and the encryption stays.
During testing, an admin created the sensitivity label Pilot and added it to the label policy Test Users. She now tries to delete Pilot on the Labels page, but the deletion doesn't go through. What should she do first?
ARemove the encryption setting from Pilot
BRemove Pilot from every document it's applied to
CWait up to 24 hours for the label policy to replicate
DRemove Pilot from the Test Users label policy
Show the answer and why
ARemove the encryption setting from Pilot
Incorrect
Encryption doesn't block the deletion; the protection template of a deleted label is archived so that protected content can still be opened.
BRemove Pilot from every document it's applied to
Incorrect
A label that's applied to content can still be deleted; the deletion then changes how that content displays the label.
CWait up to 24 hours for the label policy to replicate
Incorrect
Replication decides when users see changes; Pilot is still in the policy, which is what blocks the deletion.
DRemove Pilot from the Test Users label policy
Correct
You can't delete a label if it's still in a label policy.
Removing a label from a label policy is less risky than deleting it and can be undone, and you can't delete a label while it's still in a label policy. When a label that applied encryption is deleted, its protection template is archived so that previously protected content can still be opened.
Users create many Loop pages without labeling them. Which label policy setting applies a label to new Loop pages without users choosing one?
AThe default label for documents and Loop components and pages
BThe default label for Power BI content
CThe default label for emails and meeting invites sent from Outlook
DThe default label for new containers
Show the answer and why
AThe default label for documents and Loop components and pages
Correct
A label policy can set a default label for unlabeled documents and Loop components and pages.
BThe default label for Power BI content
Incorrect
That default applies to Power BI content, not to Loop.
CThe default label for emails and meeting invites sent from Outlook
Incorrect
That default applies to emails and meeting invites.
DThe default label for new containers
Incorrect
That default applies to new groups and sites when labels are enabled for containers.
A sensitivity label policy can specify a default label for unlabeled documents and Loop components and pages, for emails and meeting invites, for new containers and for Power BI content. Users can change the applied default label.
A site owner removes the sensitivity label from a SharePoint site that's protected with a label. What happens?
AThe change is blocked until a compliance admin approves it
BSharePoint emails the site owners and admins about the change
CNothing is recorded, because only file labels are audited
DThe activity is audited, and no email is sent automatically
Show the answer and why
AThe change is blocked until a compliance admin approves it
Incorrect
Owners can add or remove a site's label; no approval is required.
BSharePoint emails the site owners and admins about the change
Incorrect
Adding or removing a site's label is audited without an automatically generated email.
CNothing is recorded, because only file labels are audited
Incorrect
Adding or removing a label to or from a site or group is audited.
DThe activity is audited, and no email is sent automatically
Correct
Adding or removing a sensitivity label on a site or group is audited but doesn't generate an email.
When somebody adds or removes a sensitivity label to or from a site or group, the activity is audited without automatically generating an email. These events are listed with the other sensitivity label activities in the audit log documentation.