Treating simulation mode as enforcement
The wrong answers mix up the DLP policy states. Options pick Block with override as the effective action in simulation without policy tips, turn the policy on right away, keep it off, or choose simulation with policy tips when users must see nothing. Simulation mode evaluates rules without enforcing them. Without policy tips, Block with override maps to Audit: users get no notification and nothing is blocked, while audit data is still collected across the locations. Keeping the policy off generates no audit data.
See it in a sample questionReversing which setting wins a conflict
The wrong answers invert precedence. Label order is priority, so Public sits at the top and the most restrictive label at the bottom, and alphabetical order breaks the justification and auto-labelling logic. For label policies, the highest order number wins, so order number 2 beats order number 0. For retention, retention wins over deletion: a 3 year delete and a 5 year retain give 5 years, then deletion once the suspended delete action applies.
See it in a sample questionAssuming every DLP location supports the same conditions
The wrong answers treat DLP conditions as identical across locations. SharePoint supports sensitivity labels but Teams does not, so a combined policy can use only conditions that both locations support, and SharePoint needs its own policy to use a label. The Teams location supports sensitive information types and trainable classifiers as content conditions. Fabric DLP does not support EDM, trainable classifiers, credential classifiers or named entities, and a policy that selects one returns no results.
See it in a sample questionGiving retention policies label-only features
The wrong answers hand item-level features to retention policies. A retention policy applies at the location level, such as a mailbox, site or OneDrive account, and cannot target selected items or declare records. Retention labels start the retention period when an item is labelled or on an event, mark items as records or regulatory records, and trigger disposition review. The OneDrive case needs both: a 7 year policy for the account and a 10 year label for the visa documents.
See it in a sample questionAssuming onboarding or user scope is enough for Endpoint DLP
The wrong answers assume a device or a user in scope is enough for Endpoint DLP to act. A policy applies at the endpoint only when both the user and the device are in scope, so policies are not pushed to every onboarded device because the user is in scope. Windows servers are not enabled for Endpoint DLP by default, so onboarded servers need the Windows servers setting turned on. Device scoping supports Microsoft Entra joined and hybrid Microsoft Entra joined devices, and excludes Microsoft Entra registered devices.
See it in a sample question