Sample question 1 — Implement and manage user identities
A medical research company labels each worker account with an internal code that states which study the person supports, and those codes change whenever staff move between programmes. Administrators keep rebuilding the same group by hand after every reshuffle, and the directory owner wants the roster to follow those codes on its own. Which configuration should the team apply?
- A. Configure the group membership as a rule that reads a custom security attribute stored on each user
- B. Assign every person to the group directly and revisit the roster during a quarterly access attestation.
- C. Create one static group per department and let a nightly script move anyone whose job code has changed.
- D. Seed the group once, then rely on a lifecycle workflow to email the owners when a new hire starts.
Answer: A. Option A is correct because the membership is defined as a rule that inspects a custom security attribute carried on each user record, so the roster follows the changing codes without anyone rebuilding it by hand. Option B retains a fixed list that a person must edit after every reshuffle, which is the manual effort the directory owner wants gone. Option C splits the population into rigid buckets and leans on a nightly job, so the roster trails behind the current codes. Option D enrols each person once and then only sends mail, so nobody is added or removed automatically.
