Module assessment

1.

The Data Security Posture Management (DSPM) Posture page shows Data discovery at a lower percentage but trending up, and Data protection at a higher percentage but trending down. What does this combination tell an administrator?

Protection is in better shape because its percentage is higher, so focus on discovery.

Discovery is improving and protection is degrading, so labeling is working but data loss prevention (DLP) coverage needs attention before the gap widens.

Both cards are within normal range, so no action is needed yet.

2.

In data security objectives, the Prevent data exfiltration objective shows a large count of affected items with a flat 30-day trend and active DLP policies already in place. The Prevent oversharing of sensitive data through AI objective shows a smaller count with a steep upward trend and no policies assigned. Which objective should be prioritized first, and why?

Prevent data exfiltration, because the count is larger.

Prevent oversharing through AI, because the gap is accelerating with no policies to slow it.

Neither, because both should be treated as equally urgent.

3.

On the AI observability page, an agent is flagged as high risk with active oversharing, 0 policies assigned, and an increasing 30-day activity trend. What does this combination indicate about the next assessment move?

The agent appears in AI observability, so it's governed appropriately.

Risk level alone determines urgency, so policy coverage and trend don't change the assessment.

The agent is ungoverned, active, and growing in use, so it belongs at the top of the priority list with a handoff to the AI policy team.

4.

In asset explorer, filtering to a SharePoint subworkload returns many assets with sensitive content but no sensitivity label. How should this finding be interpreted?

Classification is failing, and the team should investigate why sensitive content isn't being detected.

Classification is working, but labels aren't being applied, so the assets fall outside label-based DLP and access controls.

The data is protected because it's already classified.

5.

The team deployed an autolabeling policy for financial documents in SharePoint two weeks ago. The unlabeled financial content trend is flat. What's the most useful conclusion before reporting back?

The policy is working, and the flat trend confirms no new unlabeled content is being created.

Two weeks isn't long enough to measure impact, so wait another month.

The policy isn't reaching the intended content, so verify its scope and targets.

Check your knowledge

Feedback