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

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

Exhibit

{
  "identity": "SensitivityLabel",
  "displayName": "Highly Confidential",
  "encryptionOff": false,
  "encryptionEnabled": true,
  "userOverrideEnabled": false,
  "encryptWithUserDefinedPermissions": false,
  "rightsManagementTemplateId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "auto-labeling": {
    "sensitiveInfoTypeIds": ["SIT-ID-12345", "SIT-ID-67890"],
    "minConfidence": 75
  }
}

Refer to the exhibit. You are reviewing a Microsoft Purview sensitivity label configuration. A user reports that a document containing a sensitive info type with confidence 80 was not automatically labeled. What is the most likely cause?

⚠ Common exam trap

It's easy for candidates to confuse the existence of a sensitivity label with the configuration of an auto-labeling policy, assuming that if a label is published, it will automatically apply to matching content, but in reality, auto-labeling requires a separate policy to be explicitly configured.

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 auto-labeling policy is not configured to apply this label.

Auto-labeling in Microsoft Purview requires a specific auto-labeling policy to be configured and published to the user or location. Even if a sensitivity label exists and a sensitive info type (SIT) is detected with high confidence, the label will not be applied automatically unless an auto-labeling policy is explicitly set to apply that label to documents matching the SIT. The user's report indicates the label was not applied, which points to the policy not being configured, not a user override or encryption issue.

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 user has overridden the label application.
Why it's wrong here
The userOverrideEnabled property is explicitly set to false in the label definition. This configuration prevents end-users from manually changing, removing, or downgrading the sensitivity label once it has been applied to content. Consequently, if this label were applied, users would not have the ability to override its application, making this statement incorrect.
✗
The encryption is disabled.
Why it's wrong here
The exhibit clearly indicates that EncryptionEnabled is set to true within the sensitivity label's configuration. This property explicitly signifies that encryption is an active protection setting associated with this label. Therefore, any content classified with this label would be subject to the defined encryption parameters, directly contradicting the statement that encryption is disabled.
✗
The encryption template ID is missing.
Why it's wrong here
The exhibit would display a specific TemplateId value, such as a GUID, indicating that an Azure Information Protection (AIP) encryption template is correctly associated with this sensitivity label. A missing encryption template ID would typically be represented by a null or empty string value for this property, which is not the case based on the premise that the template ID is present.
✓
The auto-labeling policy is not configured to apply this label.
Why this is correct
While a sensitivity label defines the specific protection settings, such as encryption and access controls, its mere existence does not automatically apply it to content. For automatic application, a distinct auto-labeling policy must be created and configured within Microsoft Purview to identify sensitive information based on specific conditions and then apply this particular label. The label definition itself is separate from its deployment via an auto-labeling policy.

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