Free SC-400 Exam Braindumps (page: 11)

Explanation:

Box 1: Yes
The sensitivity label policy Policy1 is published to User2.
Policy1 include the label General.

Note: What label policies can do
After you create your sensitivity labels, you need to publish them to make them available to people and services in your organization. The sensitivity labels can then be applied to Office documents and emails, and other items that support sensitivity labels.

Box 2: No
Policy3 is published to User1.
Policy3 has higher Order (2) compared to Policy1 (0) and Policy2 (1).
For Policy3, the default label for documents is Secret/Medium.
The default document label for User1 is Secret/Medium.

(The sensitivity label policy Policy1 is published to User1.
For Policy1, the default label for documents is Confidential/Low.
Policy1 has order 0 (lowest).
User1 is a member of Group1.
Policy2 is published to Group1.
For Policy2, the default label for documents is Secret/Low.
Policy2 has order 1.)

Note: A label policy consists of:
A set of labels.
The users and groups that will be assigned the policy with labels.
The scope of the policy and policy settings for that scope (such as default label for files and emails).

You can include a user in multiple label policies, and the user will get all the sensitivity labels and settings from those policies. If there is a conflict in settings from multiple policies, the settings from the policy with the highest priority (highest order number) is applied. In other words, the highest priority wins for each setting.

Box 3: Yes
Policy1 includes the Confidential label.
Policy1 is published to User1.

Note: You can include a user in multiple label policies, and the user will get all the sensitivity labels and settings from those policies.

Reference:

https://learn.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels?view=o365-worldwide#what-label-policies-can-do

Explanation:

You can only set expiration dates for emails to external recipients.

With Microsoft Purview Advanced Message Encryption, anytime you apply custom branding, the Office 365 applies the wrapper to email that fits the mail flow rule to which you apply the template. In addition, you can only use expiration if you use custom branding.

Note: Create a custom branding template to force mail expiration by using PowerShell
1. Connect to Exchange Online PowerShell with an account that has global administrator permissions in your organization.

2. Run the New-OMEConfigurationcmdlet.

PowerShell
New-OMEConfiguration -Identity "Expire in 7 days" -ExternalMailExpiryInDays 7

Where:

Identity is the name of the custom template.

ExternalMailExpiryInDays identifies the number of days that recipients can keep mail before it expires. You can use any value between 1–730 days.

Reference:

https://learn.microsoft.com/en-us/microsoft-365/compliance/ome-advanced-expiration

Explanation:

Box 1: No
Policy1 will be applied. Policy1 has an exception for user4@fabrikam. The processing is stopped at Policy1.

Note: Data loss prevention (DLP) policies are processed in a specific order. This process is called policy precedence. The policy with the lowest priority number is processed first. The first rule is configured as a priority “0” by default, the next one as “1”, and so on.

Conditions are inclusive and are where you define what you want the rule to look for and context in which those items are being used.

Box 2: Yes
Policy1 will be applied.

Box 3: No
Policy2 will be applied.

Reference:

https://learn.microsoft.com/en-us/microsoft-365/compliance/dlp-policy-reference

Explanation: