Free Microsoft Dynamics MB-310 Actual Exam Questions - Question 15 Discussion
You need to determine the root cause for User1’s issue.
Which configuration options should you check? To answer, select the appropriate options in the
answer area.
NOTE: Each correct selection is worth one point.

B for sign-in logs confirms if User1 actually attempted access.
I’d add that C could be worth checking if the problem involves multi-factor authentication hiccups—sometimes MFA settings trip people up even if sign-in logs look okay. Also, D is important because user permissions or role assignments often cause access issues. So, B definitely for the logs, and then D for the user’s access rights. A might be less urgent unless there’s a mention of device compliance policies specifically blocking User1.
I’m thinking B and D make the most sense to check here. B covers sign-in logs, which are key for spotting authentication problems, and D looks at user access-related settings. A’s about device compliance, but unless the question mentions conditional access or device-based blocks, it might be less critical. C seems off since there’s no clear MFA issue mentioned. So, focusing on sign-in behavior and user permissions should help pinpoint the root cause better.
I’d focus on B and D since they cover sign-in logs and user access. A might be less relevant without clear device compliance info, and C seems unrelated unless MFA is explicitly causing trouble here.
I’d say A and B are worth checking here because device compliance (A) can block access even if user permissions (B) look fine. Sometimes users get stuck due to device policy conflicts before sign-in issues show up. D’s about user sign-in status, but if the device isn’t compliant, that might be the root cause before sign-in problems appear. So, I wouldn’t overlook A just yet since device restrictions often cause these kinds of access problems.
I’d rule out C because it’s about multi-factor settings, which might not cause this issue. B and D look more directly related to user access permissions and sign-in status.
I’d skip A since it’s about device policies, not user access. B and D focus more on login and permission issues, so those make more sense to check first.
B and D seem more linked to user access problems than A or C.
I’m thinking options B and C, since A looks like a common trap here.