Microsoft MD-102 Practice Test 2
Question 10
A firm wants a cloud device group populated automatically when Windows devices have a specified enrollment profile attribute. Someone suggests: Maintain a static group with a weekly emailed spreadsheet. Which finding BEST explains why that proposed shortcut should be rejected?
- The shortcut can be accepted without any validation because the setting has a familiar name.
- A work account alone does not prove corporate device ownership
- Enrollment success must be reconciled with the expected cloud identity object
- Manual lists drift when devices are added or removed
Explanation
Correct Answer
D:Manual lists drift when devices are added or removed. It directly explains why the proposal Maintain a static group with a weekly emailed spreadsheet is deficient.
Incorrect Answers
A:A familiar policy or product name cannot establish effectiveness. The concrete deficiency is: Manual lists drift when devices are added or removed.
B:This finding concerns another case: An enterprise wants help-desk staff to identify corporate versus personally registered endpoints from the device directory. The decisive distinction here is: Manual lists drift when devices are added or removed.
C:This is relevant to a different objective decision: A deployment engineer enrolls Windows machines but cannot locate the cloud device object for several machines, not the present deficient proposal. This proposal flaw decision instead concerns: A firm wants a cloud device group populated automatically when Windows devices have a specified enrollment profile attribute.
Question 11
A firm wants a cloud device group populated automatically when Windows devices have a specified enrollment profile attribute. After implementing Define and validate a dynamic device membership rule in Microsoft Entra, which observation BEST demonstrates that the intended control is working?
- The owner approved Define and validate a dynamic device membership rule in Microsoft Entra on paper without testing its operation.
- A sampled owner-operated device appears as personal and fleet laptops appear corporate
- A matching test device enters the group and a nonmatching one remains out
- The team intends to test whether A matching test device enters the group and a nonmatching one remains out sometime after deployment, but has not done so.
Explanation
Correct Answer
C:A matching test device enters the group and a nonmatching one remains out. This directly verifies the intended outcome: Dynamic membership updates from device attributes rather than manual entries.
Incorrect Answers
A:Formal approval is not operating evidence. A stronger check is: A matching test device enters the group and a nonmatching one remains out.
B:This observation belongs to a different requirement: An enterprise wants help-desk staff to identify corporate versus personally registered endpoints from the device directory. The decisive distinction here is: A matching test device enters the group and a nonmatching one remains out.
D:The needed observation is: A matching test device enters the group and a nonmatching one remains out.
Question 12
The initial requirement was: A firm wants a cloud device group populated automatically when Windows devices have a specified enrollment profile attribute. Its original control is already in place. Now A temporary exception requires adding a named device immediately regardless of attribute. Which ADDITIONAL action BEST addresses the changed need?
- Define and validate a dynamic device membership rule in Microsoft Entra
- Use a governed assigned group for the explicit exception
- Maintain a static group with a weekly emailed spreadsheet
- A matching test device enters the group and a nonmatching one remains out
Explanation
Correct Answer
B:The new requirement is: A temporary exception requires adding a named device immediately regardless of attribute. The additional measure is: Use a governed assigned group for the explicit exception.
Incorrect Answers
A:This is the already implemented original control: Define and validate a dynamic device membership rule in Microsoft Entra. Dynamic membership updates from device attributes rather than manual entries.
C:This shortcut remains unsuitable. Manual lists drift when devices are added or removed.
D:This is verification of the original control, not a new action: A matching test device enters the group and a nonmatching one remains out.
Question 13
A hospital still uses local Active Directory machine accounts and needs a transitional cloud device identity with existing domain sign-in. Which recommendation BEST meets the current endpoint-management requirement?
- Define and validate a dynamic device membership rule in Microsoft Entra
- Delete the on-premises computer accounts before testing cloud sign-in
- Plan Microsoft Entra hybrid joined devices where supported and justified
- Switch new corporate devices to direct Entra join
Explanation
Correct Answer
C:Hybrid join connects legacy domain membership with cloud device registration. The selected control is: Plan Microsoft Entra hybrid joined devices where supported and justified.
Incorrect Answers
A:This is a legitimate approach for a different issue: A firm wants a cloud device group populated automatically when Windows devices have a specified enrollment profile attribute. The decisive distinction here is: Hybrid join connects legacy domain membership with cloud device registration.
B:Removing domain accounts disrupts the required legacy access model. This proposed action does not meet the stated requirement: Delete the on-premises computer accounts before testing cloud sign-in.
D:Switch new corporate devices to direct Entra join is appropriate after this separate change: The hospital retires its last AD dependency for replacement machines.
Question 14
A hospital still uses local Active Directory machine accounts and needs a transitional cloud device identity with existing domain sign-in. Someone suggests: Delete the on-premises computer accounts before testing cloud sign-in. Which finding BEST explains why that proposed shortcut should be rejected?
- The shortcut can be accepted without any validation because the setting has a familiar name.
- Removing domain accounts disrupts the required legacy access model
- Enrollment success must be reconciled with the expected cloud identity object
- Manual lists drift when devices are added or removed
Explanation
Correct Answer
B:Removing domain accounts disrupts the required legacy access model. It directly explains why the proposal Delete the on-premises computer accounts before testing cloud sign-in is deficient.
Incorrect Answers
A:A familiar policy or product name cannot establish effectiveness. The concrete deficiency is: Removing domain accounts disrupts the required legacy access model.
C:This is relevant to a different objective decision: A deployment engineer enrolls Windows machines but cannot locate the cloud device object for several machines, not the present deficient proposal. This proposal flaw decision instead concerns: A hospital still uses local Active Directory machine accounts and needs a transitional cloud device identity with existing domain sign-in.
D:This finding concerns another case: A firm wants a cloud device group populated automatically when Windows devices have a specified enrollment profile attribute. The decisive distinction here is: Removing domain accounts disrupts the required legacy access model.
Question 15
A hospital still uses local Active Directory machine accounts and needs a transitional cloud device identity with existing domain sign-in. After implementing Plan Microsoft Entra hybrid joined devices where supported and justified, which observation BEST demonstrates that the intended control is working?
- A matching test device enters the group and a nonmatching one remains out
- A test endpoint reports both domain joined and hybrid cloud registration with correct identity
- The owner approved Plan Microsoft Entra hybrid joined devices where supported and justified on paper without testing its operation.
- The team intends to test whether A test endpoint reports both domain joined and hybrid cloud registration with correct identity sometime after deployment, but has not done so.
Explanation
Correct Answer
B:A test endpoint reports both domain joined and hybrid cloud registration with correct identity. This directly verifies the intended outcome: Hybrid join connects legacy domain membership with cloud device registration.
Incorrect Answers
A:This observation belongs to a different requirement: A firm wants a cloud device group populated automatically when Windows devices have a specified enrollment profile attribute. The decisive distinction here is: A test endpoint reports both domain joined and hybrid cloud registration with correct identity.
C:A stronger check is: A test endpoint reports both domain joined and hybrid cloud registration with correct identity.
D:The needed observation is: A test endpoint reports both domain joined and hybrid cloud registration with correct identity.
Question 16
The initial requirement was: A hospital still uses local Active Directory machine accounts and needs a transitional cloud device identity with existing domain sign-in. Its original control is already in place. Now The hospital retires its last AD dependency for replacement machines. Which ADDITIONAL action BEST addresses the changed need?
- Switch new corporate devices to direct Entra join
- A test endpoint reports both domain joined and hybrid cloud registration with correct identity
- Delete the on-premises computer accounts before testing cloud sign-in
- Plan Microsoft Entra hybrid joined devices where supported and justified
Explanation
Correct Answer
A:The new requirement is: The hospital retires its last AD dependency for replacement machines. The additional measure is: Switch new corporate devices to direct Entra join.
Incorrect Answers
B:This is verification of the original control, not a new action: A test endpoint reports both domain joined and hybrid cloud registration with correct identity.
C:This shortcut remains unsuitable. Removing domain accounts disrupts the required legacy access model.
D:This is the already implemented original control: Plan Microsoft Entra hybrid joined devices where supported and justified. Hybrid join connects legacy domain membership with cloud device registration.
Question 17
An administrator cannot tell whether a Windows 11 device is Entra joined or merely workplace registered. Which recommendation BEST meets the current endpoint-management requirement?
- Infer join type solely from the device display name
- Inspect device registration and join state with dsregcmd /status
- Investigate the user SSO and PRT status rather than only the join flag
- Inventory current join state and define separate migration paths
Explanation
Correct Answer
B:Device state diagnostics distinguish joined, domain joined and workplace registered properties. The selected control is: Inspect device registration and join state with dsregcmd /status.
Incorrect Answers
A:Naming is not authoritative device identity evidence. This proposed action does not meet the stated requirement: Infer join type solely from the device display name.
C:Investigate the user SSO and PRT status rather than only the join flag is appropriate after this separate change: A later issue is that a joined device lacks a usable primary refresh token.
D:This is a legitimate approach for a different issue: An IT team must prepare a bulk migration where some Windows machines are Entra joined and others remain hybrid joined. The decisive distinction here is: Device state diagnostics distinguish joined, domain joined and workplace registered properties.
Question 18
An administrator cannot tell whether a Windows 11 device is Entra joined or merely workplace registered. Someone suggests: Infer join type solely from the device display name. Which finding BEST explains why that proposed shortcut should be rejected?
- Naming is not authoritative device identity evidence
- Uniform reset risks breaking domain dependent workloads and device state
- Enrollment success must be reconciled with the expected cloud identity object
- The shortcut can be accepted without any validation because the setting has a familiar name.
Explanation
Correct Answer
A:Naming is not authoritative device identity evidence. It directly explains why the proposal Infer join type solely from the device display name is deficient.
Incorrect Answers
B:This finding concerns another case: An IT team must prepare a bulk migration where some Windows machines are Entra joined and others remain hybrid joined. The decisive distinction here is: Naming is not authoritative device identity evidence.
C:This is relevant to a different objective decision: A deployment engineer enrolls Windows machines but cannot locate the cloud device object for several machines, not the present deficient proposal. This proposal flaw decision instead concerns: An administrator cannot tell whether a Windows 11 device is Entra joined or merely workplace registered.
D:A familiar policy or product name cannot establish effectiveness. The concrete deficiency is: Naming is not authoritative device identity evidence.
Question 19
An administrator cannot tell whether a Windows 11 device is Entra joined or merely workplace registered. After implementing Inspect device registration and join state with dsregcmd /status, which observation BEST demonstrates that the intended control is working?
- The team intends to test whether AzureAdJoined and WorkplaceJoined fields match the expected device relationship sometime after deployment, but has not done so.
- The owner approved Inspect device registration and join state with dsregcmd /status on paper without testing its operation.
- AzureAdJoined and WorkplaceJoined fields match the expected device relationship
- Pilot devices follow their intended join-specific process with maintained user access
Explanation
Correct Answer
C:AzureAdJoined and WorkplaceJoined fields match the expected device relationship. This directly verifies the intended outcome: Device state diagnostics distinguish joined, domain joined and workplace registered properties.
Incorrect Answers
A:The needed observation is: AzureAdJoined and WorkplaceJoined fields match the expected device relationship.
B:A stronger check is: AzureAdJoined and WorkplaceJoined fields match the expected device relationship.
D:This observation belongs to a different requirement: An IT team must prepare a bulk migration where some Windows machines are Entra joined and others remain hybrid joined. The decisive distinction here is: AzureAdJoined and WorkplaceJoined fields match the expected device relationship.
Question 20
The initial requirement was: An administrator cannot tell whether a Windows 11 device is Entra joined or merely workplace registered. Its original control is already in place. Now A later issue is that a joined device lacks a usable primary refresh token. Which ADDITIONAL action BEST addresses the changed need?
- AzureAdJoined and WorkplaceJoined fields match the expected device relationship
- Investigate the user SSO and PRT status rather than only the join flag
- Inspect device registration and join state with dsregcmd /status
- Infer join type solely from the device display name
Explanation
Correct Answer
B:The new requirement is: A later issue is that a joined device lacks a usable primary refresh token. The additional measure is: Investigate the user SSO and PRT status rather than only the join flag.
Incorrect Answers
A:This is verification of the original control, not a new action: AzureAdJoined and WorkplaceJoined fields match the expected device relationship.
C:This is the already implemented original control: Inspect device registration and join state with dsregcmd /status. Device state diagnostics distinguish joined, domain joined and workplace registered properties.
D:This shortcut remains unsuitable. Naming is not authoritative device identity evidence.