MD-102 Device check-in interval Practice Question
A user reports that their Windows 10 device is not receiving configuration policies from Intune. The device shows as 'Enrolled' but the last check-in was 5 days ago. What is the most likely cause?
⚠ Common exam trap
Do not assume that a check-in time of 5 days automatically means the device is within the acceptable range; the issue here is connectivity, not inactivity.
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 device is connected through a VPN that blocks Intune traffic.
The most likely cause is that the device is connected through a VPN that blocks Intune traffic. Intune requires direct internet access to communicate with its service. If the VPN restricts or filters this traffic, the device may remain enrolled but unable to check in or receive policies. Option B is incorrect because the device last checked in 5 days ago, which is within the 7-day window, so it would not be marked inactive. Option C is incorrect because the device shows as 'Enrolled'. Option D is incorrect because the Intune Connector for Active Directory is used for hybrid Azure AD join scenarios, not for direct policy delivery to enrolled devices.
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 connected through a VPN that blocks Intune traffic.
Why this is correct
Correct. A VPN that blocks Intune traffic can prevent the device from communicating with the Intune service, causing the device to appear enrolled but not receive policies. The last check-in being 5 days ago suggests a persistent connectivity issue.
- ✗
The device has not checked in for more than 7 days, causing Intune to mark it as inactive.
Why it's wrong here
Incorrect. The device last checked in only 5 days ago, which is within the 7-day inactive threshold. Intune would not mark it inactive, so this is not the cause.
- ✗
The device has been unenrolled from Intune.
Why it's wrong here
Incorrect. The device shows as 'Enrolled', so it has not been unenrolled.
- ✗
The Intune Connector for Active Directory is not configured.
Why it's wrong here
Incorrect. The Intune Connector for Active Directory is used for hybrid Azure AD join, not for policy delivery to already enrolled devices.
Visual reference
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
Hybrid Azure AD join
Hybrid Azure AD join is a Microsoft identity configuration that registers on-premises domain-joined devices with Azure Active Directory (Azure AD) to enable single sign-on and access to both on-premises and cloud resources.
About these practice questions
Courseiva writes every MD-102 question from scratch — 942 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.