Question

Group nesting is enabled between parent-child domain PRACTICELABS and NAMERICA. A domain user SalesUser1 from the NAMERICA child domain is a member of GSales Security group. GSales was unintentionally changed to a Distribution group. When SalesUser1 signed-in after a short break, he is unable to connect to the shared resource from the PRACTICELABS domain. GSales was changed back to being a Security group type. However, SalesUser1 is still unable to access the shared resource. What can you do to resolve this issue?

A. Ask SalesUser1 to sign out and sign back in as Guest.
B. Add SalesUser1 as a member of the Domain Users group in the parent domain.
C. Ask SalesUser1 to sign out and sign back in.
D. Add SalesUser1 as a member of the Domain Users group in the child domain.

Answer 1

To resolve the access issue for SalesUser1 who is unable to connect to a shared resource after GSales group was corrected from Distribution to Security group type, SalesUser1 should sign out and sign back in to get a new security token with updated permissions.

Step-by-step explanation:

The issue here is that after GSales was changed back from a Distribution group to a Security group, the permissions associated with it do not immediately reflect in the user's login session. In this case, SalesUser1 is unable to access the shared resource because the security token that was issued at the time of login does not have the updated group membership information. The correct course of action would be:

C. Ask SalesUser1 to sign out and sign back in.

This is because when SalesUser1 logs in again, a new security token that includes the updated group memberships will be generated. This will allow the necessary access permissions to the shared resource on the PRACTICELABS domain.