How does aggregation affect user names in multiple directories?

How does aggregation affect user names in multiple directories?

• A. Only the first directory's memberships are used.
• B. Memberships are chosen from a single directory.
• C. Aggregate membership combines group memberships from all directories.
• D. Aggregation duplicates memberships.

Answer: (C)

Aggregation combines a user’s group memberships from every configured directory into one set, so the user’s permissions reflect the union of those memberships. This means if a user belongs to a group in one directory and another group in a different directory, both groups contribute to the user’s access. It’s not limited to the first directory or to a single directory; the point of aggregation is to pull from all sources and merge them. While it’s possible to encounter the same group name in different directories, the system typically resolves duplicates so you don’t get conflicting or doubled permissions. For example, membership in an Admins group in directory A and an Editors group in directory B would grant permissions associated with both groups.

Aggregation combines a user’s group memberships from every configured directory into one set, so the user’s permissions reflect the union of those memberships. This means if a user belongs to a group in one directory and another group in a different directory, both groups contribute to the user’s access. It’s not limited to the first directory or to a single directory; the point of aggregation is to pull from all sources and merge them. While it’s possible to encounter the same group name in different directories, the system typically resolves duplicates so you don’t get conflicting or doubled permissions. For example, membership in an Admins group in directory A and an Editors group in directory B would grant permissions associated with both groups.