Endpoint Administrator MD-102 Practice Test 3
Question 20
An engineer increased the Intune device enrollment limit, but the same employee still gets a maximum-devices message while joining Windows to Microsoft Entra. What policy comparison resolves the discrepancy?
- Compare the separate Microsoft Entra device-registration maximum with the Intune enrollment limit and identify which limit applies to this join method
- Treat the changed Intune device cap as proof the Entra device limit also changed
- Reclassify all existing devices as personal without reviewing the join registrations
- Assume the MDM user scope is the rejecting limit despite an explicit max-devices join message
Explanation
Correct Answer
A:Two product limits exist; increasing one does not necessarily change the limit that rejected the Entra join.
Incorrect Answers
B:The caps are separate settings and require an explicit check of which one rejected the join.
C:Ownership labeling cannot establish whether the Entra user quota has been exhausted.
D:MDM scope affects automatic management, but the recorded rejection is at Entra device capacity.
Question 21
After correcting the actual Entra quota problem for one affected user, what evidence is more convincing than an increased numeric limit in the portal?
- A different user joins a different PC successfully
- The same user successfully joins the pilot Windows device, a new corresponding Entra device identity appears, and nonpilot join restrictions remain in effect
- The Entra limit value increases in the admin center, but the affected user has not retried
- The device appears in an enrollment group but is still not Entra joined
Explanation
Correct Answer
B:Real device join plus preserved population boundaries validates the change rather than treating a policy number as a completed enrollment.
Incorrect Answers
A:Another user does not exercise the quota that blocked the affected employee.
C:Configuration evidence is not proof of a successful previously denied join.
D:Group membership alone is not the required successful device identity registration outcome.
Question 22
Domain-joined Windows laptops should hybrid join the organization’s Microsoft Entra tenant. `dsregcmd /status` shows `DomainJoined : YES`, `AzureAdJoined : NO`, and pre-join diagnostics report `DSREG_AUTOJOIN_ADCONFIG_READ_FAILED`. What should the engineer inspect first?
- Reconfigure Intune automatic MDM enrollment scope without inspecting hybrid SCP discovery
- Force a Microsoft Entra Connect computer-object sync without checking the invalid SCP
- Validate the Active Directory service connection point configuration for the correct Entra tenant and its discoverability by these domain-joined devices
- Widen federation authentication access to internet clients before resolving the SCP read error
Explanation
Correct Answer
C:The reported error identifies failure reading the SCP configuration used to locate the Entra tenant for hybrid registration.
Incorrect Answers
A:MDM eligibility does not correct the failure to read tenant discovery metadata from AD.
B:Object synchronization alone will not fix a device failing its SCP configuration read.
D:The reported error occurs at tenant configuration discovery, before federation authentication.
Question 23
A regional Windows 11 domain-joined pilot reaches Active Directory but its hybrid-join diagnostic says tenant discovery fails before authentication. The engineer suspects an incorrect SCP tenant ID. Which observation would specifically confirm that hypothesis?
- The Intune MDM user scope is set to Some rather than All
- The device group has a delayed membership evaluation
- A user receives an MFA challenge during application access
- The SCP tenant discovery values exposed to the affected devices do not match the intended Microsoft Entra tenant identifiers
Explanation
Correct Answer
D:The explicit discrepancy lies at tenant discovery, prior to user sign-in or Intune enrollment evaluation.
Incorrect Answers
A:This affects downstream enrollment and does not prove the client’s AD SCP tenant identifier is wrong.
B:Group evaluation occurs after the device identity is available, not before tenant SCP discovery.
C:An app authentication prompt does not identify the tenant values contained in the domain SCP.
Question 24
The SCP tenant metadata for the hybrid-join pilot was corrected. What test most directly demonstrates that the Windows identity-state blocker is resolved?
- The machine resolves and contacts its on-premises domain controller
- On a targeted domain-joined computer, `dsregcmd /status` shows `DomainJoined : YES` and `AzureAdJoined : YES` and the Entra tenant/device identifiers correspond to the intended tenant
- The Entra device record exists but the local system still shows `AzureAdJoined : NO`
- The Intune portal shows a device name with no local identity-state data
Explanation
Correct Answer
B:Those status flags and tenant identifiers demonstrate hybrid identity registration, not merely domain connectivity.
Incorrect Answers
A:Traditional AD connectivity alone does not prove it acquired Entra hybrid device identity.
C:A record alone cannot establish successful device join on the actual Windows client.
D:A stale inventory display does not prove the target device completed hybrid join.
Question 25
An employee owns a Windows laptop and wants one work account available to Office apps without converting the personal machine into a corporate Entra-joined device. Which identity action matches that boundary?
- Use the Windows “Join this device to Microsoft Entra ID” path when only a work-account registration is intended
- Enable hybrid join through the corporate on-premises AD for the home laptop
- Create an Intune managed device record manually and assume it makes the personal device registered
- Add the work account to Windows for application access and use Microsoft Entra registration rather than selecting organization-wide Microsoft Entra device join
Explanation
Correct Answer
D:Registration is the workplace identity state suitable for this personal-device access case; device join establishes a different device ownership/identity relationship.
Incorrect Answers
A:That explicitly performs an organization device join rather than simple per-user workplace registration.
B:Hybrid join introduces a domain-joined device state that is not requested for this personal machine.
C:Administrative inventory cannot replace an actual per-user workplace identity registration.
Question 26
A user says a personal Windows device was merely registered for Microsoft 365. `dsregcmd /status` shows `AzureAdJoined : YES`, `DomainJoined : NO`. What is the precise problem with that claim?
- `AzureAdJoined : YES`, `DomainJoined : NO` describes per-user workplace registration only
- `AzureAdJoined : YES`, `DomainJoined : NO` proves the computer is hybrid joined
- The observed state is Microsoft Entra joined, not just per-user Microsoft Entra registered
- Any successful Microsoft 365 app login establishes the machine’s registered-only state
Explanation
Correct Answer
C:The AzureAdJoined/DomainJoined combination describes the device-wide join state; workplace registration is reported under the user context instead.
Incorrect Answers
A:That combination is cloud Entra device join rather than registered-only state.
B:Hybrid join requires DomainJoined YES in addition to AzureAdJoined YES.
D:An application sign-in can occur independently of a particular device join/registration classification.
Question 27
A personal Windows device should remain only Microsoft Entra registered after the owner adds a work account. Which `dsregcmd /status` evidence is most relevant when run in that user’s context?
- `AzureAdJoined : YES`, `DomainJoined : NO` with no workplace evidence
- `AzureAdJoined : YES`, `DomainJoined : YES`
- A work account is listed in an app but no workplace user-state data was collected
- Device state is not AzureAdJoined and the relevant user state reports `WorkplaceJoined : YES` for the added work account
Explanation
Correct Answer
D:A workplace-registered user identity is reported under User State rather than as a device-wide Entra join.
Incorrect Answers
A:This is organization device join, not the specified personal registration-only state.
B:Both device flags YES indicate hybrid join, not merely per-user workplace registration.
C:App-account presence is not sufficient to confirm the requested Windows registration state.
Question 28
An administrator wants an Entra dynamic device group to contain Windows Autopilot hardware with purchase-order identifier `76222342342`, not all Windows devices. Which membership attribute and condition should be used?
- `device.devicePhysicalIds -any _ -eq "[PurchaseOrderId]:76222342342"`
- `device.devicePhysicalIds -any _ -startsWith "[ZTDId]"`
- `device.deviceOSType -eq "Windows"`
- `device.devicePhysicalIds -any _ -eq "[OrderID]:76222342342"`
Explanation
Correct Answer
A:Microsoft Entra dynamic device rules expose Autopilot purchase order metadata through devicePhysicalIds; an exact-value condition scopes this procurement cohort.
Incorrect Answers
B:That matches the general Autopilot inventory rather than the required procurement order subset.
C:The rule would collect unrelated Windows endpoints with different purchase orders.
D:OrderID is an Autopilot group-tag field; the scenario specifically calls for a PurchaseOrderId property.
Question 29
A procurement pilot requires only Autopilot serials tagged by a specific purchase order. A dynamic group currently uses `(device.devicePhysicalIds -any _ -startsWith "[ZTDId]")` and includes every registered Autopilot device. Why is the assignment overly broad?
- The `[ZTDId]` starts-with condition recognizes Autopilot devices generally rather than the required purchase-order value
- The `[ZTDId]` rule selects only the stated purchase order
- The procurement group is empty because no users were directly assigned
- All Autopilot devices share one purchase order by design
Explanation
Correct Answer
A:The tested distinction is Autopilot inventory as a whole versus devices with a specific purchase order ID.
Incorrect Answers
B:The marker identifies Autopilot inventory broadly, not a single order number.
C:This is a dynamic device group based on hardware attributes, not a user assigned membership list.
D:Autopilot registry may contain many purchase order values; the rule must check the requested one.
Question 30
After deploying the purchase-order-based dynamic rule, what enrollment-time evidence demonstrates correct group targeting before applying a high-risk policy?
- The dynamic group contains every Autopilot device regardless of purchase order
- Matching devices are included but a different purchase-order device is also included
- The rule text is present, but there are no devices or evaluated memberships
- Test serials with matching `[PurchaseOrderId]` populate the dynamic group while comparable Autopilot serials from a different purchase order are excluded
Explanation
Correct Answer
D:A positive and negative hardware sample verifies the intended procurement segmentation rather than mere group existence.
Incorrect Answers
A:That verifies a generic ZTD grouping but fails required procurement isolation.
B:Positive-only selection is insufficient; the rule leaks unrelated procurement hardware.
C:Saving a dynamic expression does not show its effective membership logic.