Describe the capabilities of Microsoft compliance solutions →mediumMultiple ChoiceObjective-mapped

SC-900 Practice Question: Describe the capabilities of Microsoft compliance solutions

Exhibit

{
  "LabelName": "Highly Confidential",
  "Tooltip": "This label is for highly confidential data.",
  "Actions": [
    {
      "ActionType": "Encrypt",
      "EncryptionSettings": {
        "EncryptionEnabled": true,
        "ProtectWithRightsManagement": true
      }
    },
    {
      "ActionType": "Marking",
      "MarkingSettings": {
        "HeaderText": "HIGHLY CONFIDENTIAL",
        "FooterText": "Do not forward"
      }
    }
  ]
}

Refer to the exhibit. You are reviewing a sensitivity label configuration in Microsoft Purview. Based on the exhibit, what is the result when a user applies this label to a document?

⚠ Common exam trap

Many candidates confuse sensitivity labels with retention labels, assuming that sensitivity labels can automatically delete or remove themselves after a time period, when in fact sensitivity labels focus on protection and marking, not lifecycle management.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The document is encrypted and a header/footer is added

The exhibit shows a sensitivity label configured with both encryption (via Azure Information Protection) and content marking (header/footer). When a user applies this label, the document is automatically encrypted to protect sensitive data, and the specified header and footer are added to the document as visual markings. This is a common configuration in Microsoft Purview Information Protection to enforce protection and awareness simultaneously.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The label is automatically removed after one year
Why it's wrong here
Sensitivity labels, unlike retention labels, do not inherently include a feature for automatic removal or expiration from a document after a set period, such as one year. Their primary function is to apply persistent classification and protection, which remains until a different label is applied or the label is manually removed. The exhibit's configuration, as indicated, does not specify any such auto-removal action.
✗
The document is automatically deleted after 30 days
Why it's wrong here
Automatic document deletion after a specified duration, like 30 days, is a function typically managed by Microsoft Purview retention policies or retention labels, not sensitivity labels. Sensitivity labels are designed for data classification, protection, and access control, not for lifecycle management actions such as deletion. The configuration described in the exhibit does not include any settings for automatic content deletion.
✓
The document is encrypted and a header/footer is added
Why this is correct
The configuration of this sensitivity label explicitly includes both encryption and visual markings, such as headers and footers. Encryption, powered by Azure Information Protection, ensures that only authorized users can access the document and defines their specific usage rights. Concurrently, visual markings provide clear, persistent indicators within the document itself, communicating its sensitivity level to all who view it.
✗
The document can be printed but not edited
Why it's wrong here
While sensitivity labels can apply granular permissions through encryption, allowing printing while restricting editing requires specific rights management configuration. The existing note indicates that these precise permissions are not explicitly set within the label's configuration. Without explicit definition of these specific usage rights, one cannot assume this exact combination of print-only, no-edit access is enforced.

Go deeper

SC-900 Practice Question: Describe the capabilities of Microsoft compliance solutions

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question