How to make Sublabel1 the default sensitivity label for Group1?
You have a Microsoft 365 subscription that contains 100 users and a Microsoft 365 group named Group1. All users have Windows 10 devices and use Microsoft SharePoint Online and Exchange Online. A sensitivity label named Label1 is published as the default label for Group1. You add two sublabels named Sublabel1 and Sublabel2 to Label1. You need to ensure that the settings in Sublabel1 are applied by default to Group1. What should you do?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This item tests where a group's default sensitivity label is actually configured, and the trap is assuming that adding or reordering a sublabel automatically inherits the parent's default status.
Group1 already has Label1 published as its default sensitivity label, and Sublabel1 is a child label added under Label1. The page establishes that the existing label policy must be modified to make Sublabel1 the default for Group1.
The common wrong choice is A, changing Sublabel1's order, because learners confuse label order or priority with the default label selected in the label policy.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The default label for a Microsoft 365 group is enforced by the sensitivity label policy that is scoped to that group, not by the parent label's own configuration. Because Label1 was already published as Group1's default, the correct action is to modify that existing label policy and select Sublabel1 as the group's default label. This preserves the published label set and applies Sublabel1's settings automatically to Group1. Option B matches that administrative path exactly.Why the Other Options Are Wrong
Changing the order of Sublabel1 (A) only affects label priority or the order in which labels appear; it does not set a default. Deleting the Label1 policy and publishing Sublabel1 (C) is unnecessarily destructive and would remove the existing Label1 publication rather than update the default. Duplicating Sublabel1's settings to Label1 (D) changes the parent label's configuration and still does not make Sublabel1 the default. None of these options address the policy-level default-label setting that Group1 requires.Community Comment Notes
SSL2 explains that when you want a specific label as the default for a group, "you adjust the label policy that applies to that group," which aligns with modifying the existing Label1 policy. emartiy notes that the other options do not provide a way to make Sublabel1 the default, and Domza simply agrees with B. Futfuyfyjfj also references an external article on default sensitivity labels for SharePoint Online, supporting the same policy-based approach. The community consensus points to B for the same technical reason.Official Reference
Exam Strategy
When a question mentions a default label for a group, immediately look for the label policy setting rather than parent-label settings. In SC-400, sublabels do not inherit default status; the default is explicitly chosen in the policy that targets the user or group.
Frequently Asked Questions
Why is changing the order of Sublabel1 not enough to make it the default?
Label order controls priority or display, not the default label applied by a scoped policy. The policy must explicitly select Sublabel1 as the default for Group1.
Should I delete the Label1 policy before publishing Sublabel1?
No. Deleting the existing policy would unpublish Label1 from Group1 and disrupt other settings; modify the current policy instead.