MD-102 Prepare infrastructure for devices Practice Question
Exhibit
{
"@odata.type": "#microsoft.graph.windows10CompliancePolicy",
"passwordRequired": true,
"passwordMinimumLength": 6,
"passwordRequiredType": "deviceDefault",
"passwordMinutesOfInactivityBeforeLock": 5,
"passwordExpirationDays": 90,
"passwordPreviousPasswordCountToBlock": 5,
"secureBootEnabled": true,
"codeIntegrityEnabled": true,
"earlyLaunchAntimalwareDriverProtectionEnabled": true,
"bitLockerEnabled": true,
"bitLockerRecoveryPasswordRotation": "disabled"
}Refer to the exhibit. You are reviewing an Intune compliance policy JSON for Windows 10. A device reports as non-compliant, and the compliance status details indicate that the setting 'Secure Boot' is not compliant. The device is a virtual machine. What is the most likely reason?
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
✓
The virtual machine does not have Secure Boot enabled in its firmware settings.
Secure Boot is a hardware-based feature that ensures the system boots using only software trusted by the PC manufacturer. In virtual machines, Secure Boot is often not enabled by default or may not be supported by the hypervisor. For Intune compliance, if the VM does not have Secure Boot enabled, it will report as non-compliant. Option C is correct because the VM's firmware settings likely have Secure Boot disabled. Option A is incorrect because the device may still be enrolled correctly. Option B is incorrect because password policy is unrelated to Secure Boot. Option D is incorrect because BitLocker is a separate encryption feature not required for Secure Boot.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The device is not enrolled in Intune correctly.
Why it's wrong here
Enrollment status would affect other settings, but specifically Secure Boot non-compliance points to hardware support.
- ✗
The password policy is conflicting with Secure Boot.
Why it's wrong here
Password policy does not affect Secure Boot.
- ✓
The virtual machine does not have Secure Boot enabled in its firmware settings.
Why this is correct
VMs often have Secure Boot disabled; enabling it in the VM settings resolves the issue.
- ✗
The device does not have BitLocker enabled, which is required for Secure Boot.
Why it's wrong here
BitLocker and Secure Boot are independent.
Go deeper
Related to this question
Learn chapter
Enrolling Devices with Microsoft Intune
Key term
Policy
A policy is a set of rules or guidelines that defines how an organization manages, secures, and operates its IT systems and services.
Key term
Encryption
Encryption is the process of converting readable data into a secret code to prevent unauthorized access.
About these practice questions
This MD-102 question is part of Courseiva's 942-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.