A good example is enforcing BitLocker on Windows devices. You can do this through a Configuration Profile. an Endpoint Security Disk Encryption policy or a Compliance Policy that just checks encryption status. All three touch BitLocker in some way, but they are not interchangeable.

If the goal is to actually turn on encryption and manage recovery keys, the Endpoint Security Disk Encryption policy is the right tool. A Compliance Policy will only report whether encryption is already enabled, it will not enforce it. A Configuration Profile can push some settings but is not the most direct path for this specific case.

MD-102 Exam Questions often test this kind of reasoning rather than asking you to recall a setting name. You need to know what each policy type is actually built to do, not just where the toggle lives.

While going through Microsoft MD-102 practice questions including some from Pass4Success. I found it useful to pause on the "why is this wrong" explanations instead of just checking the right answer. That habit helped more than memorizing screens.

Curious if others found similar overlap traps in the compliance vs configuration profile area or somewhere else in the exam.