The answer is Hybrid Azure AD join. This approach is correct because it enables devices already joined to on-premises Active Directory to register with Microsoft Entra ID, allowing Intune to manage them while they continue authenticating to on-premises resources via Kerberos or NTLM without a VPN. Azure AD Connect synchronizes the device object from AD to Entra ID, creating a single device identity that works seamlessly across both cloud and on-premises services. On the MD-102 exam, this scenario tests your understanding of how to bridge legacy on-premises access with modern cloud management—a common trap is confusing Hybrid Azure AD join with pure Azure AD join, which would break on-premises resource access. Remember the key distinction: Hybrid join keeps the on-premises domain membership intact while adding cloud registration. Memory tip: think “Hybrid = Handshake” — the device shakes hands with both your local domain controller and Intune in the cloud.
MD-102 Manage and maintain devices Practice Question
This MD-102 practice question tests your understanding of manage and maintain devices. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are designing a device management strategy for a hybrid environment with on-premises Active Directory and Microsoft Entra ID. You need to ensure that devices are managed by Intune and can access on-premises resources. Which approach should you recommend?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Hybrid Azure AD join
Hybrid Azure AD join is the correct approach because it allows devices that are joined to on-premises Active Directory to also register with Microsoft Entra ID, enabling Intune management while maintaining access to on-premises resources via Kerberos/NTLM authentication. This configuration synchronizes the device object from AD to Entra ID using Azure AD Connect, creating a device identity that can be managed by Intune and can authenticate against both cloud and on-premises services without requiring a VPN.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Hybrid Azure AD join
Why this is correct
Hybrid Azure AD join allows devices to be joined to both on-premises AD and Entra ID, enabling Intune management and on-premises resource access.
Related concept
Read the scenario before looking for a memorised answer.
✗
Entra ID registered with on-premises domain join
Why it's wrong here
Entra ID registered devices are not domain-joined.
✗
Windows Autopilot self-deploying mode
Why it's wrong here
Autopilot is a provisioning method, not a join type.
✗
Entra ID joined with VPN to on-premises
Why it's wrong here
Entra ID joined devices cannot access on-premises resources without additional configuration.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'Entra ID registered' with 'Hybrid Azure AD join' because both involve Entra ID, but only Hybrid Azure AD join provides the on-premises domain join required for seamless resource access without a VPN.
Detailed technical explanation
How to think about this question
Hybrid Azure AD join relies on the Azure AD Connect sync engine to write back the device registration state to on-premises AD via the msDS-DeviceID attribute, and the device itself uses the System Context (SYSTEM account) to authenticate to Entra ID using a certificate issued by the on-premises AD. A subtle behavior is that the device must have line-of-sight to a domain controller during the registration process, and the SCP (Service Connection Point) in AD must be configured correctly; otherwise, the join fails silently. In real-world scenarios, this approach is critical for organizations that need to apply Intune policies (e.g., BitLocker, compliance) while still allowing users to access on-premises file servers and printers without additional infrastructure.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this MD-102 question in full detail.
Manage and maintain devices — This question tests Manage and maintain devices — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Hybrid Azure AD join — Hybrid Azure AD join is the correct approach because it allows devices that are joined to on-premises Active Directory to also register with Microsoft Entra ID, enabling Intune management while maintaining access to on-premises resources via Kerberos/NTLM authentication. This configuration synchronizes the device object from AD to Entra ID using Azure AD Connect, creating a device identity that can be managed by Intune and can authenticate against both cloud and on-premises services without requiring a VPN.
What should I do if I get this MD-102 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.