Question 980
Scenario: A newly created Secret label exists in Purview but no members of the pilot team can select it in Office apps. What technical conclusion best explains the situation?
Explanation
Correct Answer
Sensitivity labels must be published through a supported label policy to the intended users. The case concerns publish a sensitivity label to a pilot group: A newly created Secret label exists in Purview but no members of the pilot team can select it in Office apps. Label definitions and their user-targeted publishing policies are separate configuration objects. This answers the key interpretation of the requirement because it addresses the explicit constraint. The decisive check is inspect label publication policy scope and the pilot user's applied labels list. The corresponding implementation would be publish the label to the relevant HR pilot group and confirm supported client policy refresh.
Incorrect Answers
Label adoption metrics require contextual sampling before interpreting compliance effectiveness. The records needed for this specific case concern: Inspect label publication policy scope and the pilot user's applied labels list.
Default labeling establishes a baseline that users and automated policies must still govern. The current corrective requirement is: Publish the label to the relevant HR pilot group and confirm supported client policy refresh.
Information protection requires durable identity group planning for protected content ownership. The appropriate acceptance check is: An authorized pilot user sees and can apply the Secret label in a supported client.