Question 280
A technical review is underway: A support operator is scoped to an administrative unit that contains a group, but members of that group are not directly in the unit. Which caveat prevents an overbroad claim about this solution?
Explanation
Correct Answer
Assuming all nested or indirect group members inherit AU-scoped user management produces access errors. The case concerns administrative unit group member nuance: A support operator is scoped to an administrative unit that contains a group, but members of that group are not directly in the unit. Administrative unit object scoping depends on direct membership and the supported operation. This answers the condition that limits a broader guarantee because it addresses the explicit constraint. Even after the main change, assuming all nested or indirect group members inherit AU-scoped user management produces access errors. Review the concrete evidence before treating the control as complete.
Incorrect Answers
Directory role selection should grant only the administrative operations required by the task. The records needed for this specific case concern: Inspect the administrative unit's direct user memberships and group object membership separately.
Teams administration is a workload role distinct from team membership and Microsoft 365 compliance roles. The current corrective requirement is: Add target user objects directly to the scoped unit where user-level administration is required.
Administrative units restrict supported directory administration, not all downstream resource permissions. The appropriate acceptance check is: A delegated test admin can act on directly scoped users but not unrelated members of an included group.