MD-102 Manage and maintain devices Practice Question
Exhibit
{
"@odata.type": "#microsoft.graph.windows10CompliancePolicy",
"displayName": "Windows 10 Compliance",
"requireDeviceEncryption": true,
"requireSecureBoot": true,
"requireCodeIntegrity": true,
"passwordRequired": true,
"passwordMinimumLength": 8
}Refer to the exhibit. You create a compliance policy for Windows 10 devices. A device is reported as non-compliant. Upon investigation, you find that the device has a password of 6 characters. Which setting is causing the non-compliance?
⚠ Common exam trap
Watch out — candidates often confuse passwordMinimumLength with password complexity or other security settings like requireCodeIntegrity or requireSecureBoot, assuming any security-related non-compliance must be due to a broader security feature rather than the specific password length.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
passwordMinimumLength
The compliance policy requires a minimum password length, and the device's 6-character password does not meet that requirement, making it non-compliant. The passwordMinimumLength setting directly controls the minimum number of characters a password must have, so a password shorter than the configured value triggers non-compliance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
requireCodeIntegrity
Why it's wrong here
requireCodeIntegrity checks that only signed, trusted drivers and code load, having no bearing on password length. It is the correct setting when a device runs unsigned or tampered kernel drivers; the non-compliance here stems from the password policy's minimum length threshold instead.
- ✓
passwordMinimumLength
Why this is correct
The compliance policy's passwordMinimumLength setting enforces a minimum character count, and the device's six-character password falls below the configured threshold, triggering non-compliance. This directly matches the stem's reported condition, where the password length is the sole identified deviation from policy requirements.
- ✗
requireDeviceEncryption
Why it's wrong here
requireDeviceEncryption evaluates BitLocker status, not password length, so a six-character password cannot trigger it. It is the right setting when a device lacks encryption and must be remediated by enabling BitLocker; here the failing control is the minimum password length requirement.
- ✗
requireSecureBoot
Why it's wrong here
requireSecureBoot verifies UEFI Secure Boot is enabled to block boot-level malware, and never inspects account credentials. It is the right setting when Secure Boot is disabled on a device; the six-character password instead breaches the minimum password length rule in the compliance policy.
Go deeper
Related to this question
Learn chapter
Implementing Windows Autopilot
Key term
Windows 10
Windows 10 is a personal computer operating system developed by Microsoft that combines the familiarity of Windows 7 with the modern features of Windows 8, designed to run on a wide range of devices from desktops to tablets.
Key term
Compliance policy
A compliance policy is a set of rules that ensures devices, users, and applications meet an organization's security and regulatory requirements before they can access corporate resources.
About these practice questions
Courseiva writes every MD-102 question from scratch — 556 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MD-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MD-102 exam.