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

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

Exhibit

Refer to the exhibit.
```powershell
$config = Get-MgInformationProtectionPolicy
$config.Labels | Where-Object {$_.DisplayName -eq "Confidential"} | Set-MgInformationProtectionPolicyLabel -Settings @{ "Color" = "Red" }
```

Refer to the exhibit. You are a compliance administrator running PowerShell to update a sensitivity label in Microsoft Purview. The command fails with an error that the label is not found. What is the most likely cause?

⚠ Common exam trap

Test-takers frequently assume any 'InformationProtection' cmdlet returns labels, but Microsoft deliberately separates policy-level and label-level cmdlets, so using the wrong one yields a 'not found' error even when the label exists.

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 cmdlet Get-MgInformationProtectionPolicy does not return labels.

The cmdlet Get-MgInformationProtectionPolicy retrieves the policy configuration but does not return individual sensitivity labels. To update a specific label, you must use Get-MgInformationProtectionSensitivityLabel to first retrieve the label object, then pipe it to Set-MgInformationProtectionSensitivityLabel. The error 'label not found' occurs because the cmdlet used does not expose labels, not because the label is missing or misspelled.

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 -Settings parameter is deprecated.
Why it's wrong here
The -Settings parameter is a valid and active parameter within the Microsoft Graph PowerShell module, particularly when managing information protection policies or related configurations. If the parameter were deprecated, the command would typically return a specific warning indicating its obsolescence or an error stating the parameter is unrecognized, rather than an issue related to the retrieval of sensitivity labels. Its validity is not the cause of the problem.
✓
The cmdlet Get-MgInformationProtectionPolicy does not return labels.
Why this is correct
The Get-MgInformationProtectionPolicy cmdlet is specifically designed to retrieve information protection policy objects, which define the overall framework for data protection within an organization. It does not enumerate or return individual sensitivity labels. To retrieve sensitivity labels, the correct cmdlet to use is Get-MgInformationProtectionSensitivityLabel, which is dedicated to managing and listing these specific classification objects.
✗
The user does not have permissions to view labels.
Why it's wrong here
If the user lacked the necessary permissions to view sensitivity labels, the PowerShell command would typically return an explicit "Access Denied," "Authorization Failed," or similar permission-related error message. The problem described (implicitly, that labels are not returned or found) indicates a fundamental mismatch in the cmdlet's function, suggesting the command is looking in the wrong place or for the wrong object type, rather than being blocked by insufficient user rights.
✗
The label name is misspelled.
Why it's wrong here
While a misspelled label name could certainly prevent a specific label from being found, the primary issue here is the incorrect cmdlet usage. If the cmdlet itself is not designed to retrieve sensitivity labels, even a perfectly spelled label name would not yield results. The error would stem from the command's inability to query for labels, rather than a specific label not matching a provided string.

Go deeper

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

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question