A user is part of the Employees LDAP group synchronized with AEM. The same user is added to the authors group in AEM. The user is then removed from the Employees group on the LDAP server. What is the result during the next synchronization with AEM?

The AEM LDAP integration synchronizes users and their group memberships from the LDAP server. When a user is removed from a synchronized group (e.g., 'Employees') in LDAP, the sync handler will remove the user from the corresponding group in AEM upon the next synchronization. However, the user's membership in AEM-local groups (e.g., 'authors'), which are not managed by LDAP, is unaffected by this process. The user object itself is not deleted from AEM unless it is removed from the LDAP server entirely (and user purging is enabled) or loses all its synchronized memberships (and orphan user cleanup is configured). In this specific scenario, only the 'Employees' group membership is removed.

A. The user would only be removed from both groups if the user account was deleted from AEM, which is not the default behavior for just a group membership change.
B. This is incorrect because the 'authors' group is local to AEM and not managed by the LDAP sync, while the 'Employees' group is the one being synchronized.
D. This is incorrect as the default synchronization behavior is to reflect removals from LDAP groups within the corresponding AEM groups.

1. Adobe Experience Manager 6.5 Documentation, "User Administration and Security," Section: "Configuring LDAP with AEM." This document describes the synchronization behavior, stating that the sync handler updates users and groups based on the LDAP source.

2. Adobe Experience Manager 6.5 Documentation, "LDAP Identity Provider," Section: "Group Properties." The configuration options show that synchronization is tied to specific LDAP groups, implying that non-synchronized (local) groups are not affected. The group.purgeUsers and user.membershipExpTime settings control user deletion, which is a separate, non-default action.