Use three requirement rows
Information governance questions often combine classification/protection, sharing activities and lifecycle. Sensitivity labels classify content and can apply configured protection. DLP policies identify, monitor and help protect sensitive information against inappropriate sharing across supported configured activities/locations. Retention settings govern lifecycle. Start with three rows rather than one broad word such as compliance. One document can have several requirements, so choosing a control for a new row need not remove a correctly configured control for an existing row.
Labels and policy scope
Sensitivity and retention labels serve different purposes and can coexist on supported content. Not every sensitivity label necessarily applies encryption; its configuration matters. A retention policy applied only to a location does not travel with an item once it leaves that container. Item-associated retention labels address a different scope. Avoid inferring that a familiar label name proves a particular protection or lifecycle setting. The relevant facts are the supported item, configured behavior and whether the requirement concerns location or item.
Availability, application and records
Publishing retention labels makes them available for users or administrators to apply. Actual assignment to a document is a separate state; an applicable auto-apply configuration is another specific arrangement, not implied by publication alone. Records management can use configured retention labels to declare records and support lifecycle/disposition review. Do not generalize one record type’s restrictions to every item or invent a legally required duration. This course uses fictional organizational requirements rather than interpreting retention law.
Worked example
Fictional teaching case: a geology archive classifies internal field notes with a sensitivity label. It now wants to control inappropriate sharing activity and manage an approved lifecycle schedule. Write separate rows for existing classification/protection, the sharing-activity policy and retention. DLP is relevant to the sharing row; appropriate retention settings address the lifecycle row. Keeping the sensitivity setting avoids treating the new controls as replacements for classification. Check each row independently: retaining a document does not decide whether a sharing activity is permitted, and blocking sharing does not define how long to retain it.
Transfer check
Change the task: a fictional records manager has published a suitable retention label, but the review asks whether a named document has actually received it. Is a publication screenshot sufficient evidence? Check basis: no. It demonstrates availability within the publication scope, not the item’s assigned label state. Seek evidence of actual application or the relevant applicable automatic arrangement. This is distinct from choosing which control purpose belongs in a requirement row; it checks whether a chosen control has actually reached the specified item.
Verify every stated requirement
An answer should preserve existing protection, choose the right lifecycle scope and avoid equating availability with application. Supported locations, conditions, licenses and configuration remain relevant in real use. No tenant policy, real records, data-loss test or legal schedule is created here. Some classification/explorer features remain coverage gaps rather than being claimed complete from this lesson’s title.
Classify the evidence before deciding the action
Microsoft Purview brings together data governance, data security and compliance experiences. A content classification result describes a relevant content characteristic; it does not by itself grant an external sharing action or prove a retention control blocks it. A fictional steward first asks what action is proposed, then checks the applicable configured policy, supported scope and access conditions. Content explorer supports examining classified content and sensitive-information locations under relevant permissions. Its latest available reported snapshot is not an instantaneous inventory of every copy. Activity explorer supplies a historical view of supported activities, so its rows answer a different question. As a transfer check, one document may have several label-change actions: a larger activity count does not make it a more complete document inventory. Compare counted objects, filters, permissions and delays before drawing a completeness conclusion.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
Learn about data loss prevention | Microsoft LearnLearn about sensitivity labels | Microsoft LearnLearn about retention policies & labels to retain or delete | Microsoft LearnRecords management for documents and emails in Microsoft 365 | Microsoft LearnMicrosoft Learn: rd-sc-purviewMicrosoft Learn: rd-sc-contentMicrosoft Learn: rd-sc-activity