Question 200
During a scheduled security audit at Linden Manufacturing, the tenant administration team identifies this issue: A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
Membership changes when a sample user department attribute changes without manual edits to every application assignment. This is the relevant proof because it tests whether the selected corrective action (Consider dynamic group membership with properly defined identity attributes where the feature is available) addressed the initiating problem (A tenant has hundreds of users manually assigned to application access despite an existing attribute-driven department membership rule) in Linden Manufacturing's plant operations and product design information environment, not merely whether a task was marked complete.
Incorrect Answers
After resource deletion the old identity can no longer be used and its former permissions are reviewed. This is useful evidence for a different situation (A system-assigned managed identity is assumed to survive after its associated Azure resource has been deleted) and action (Recognize that a system-assigned managed identity follows the lifecycle of its associated resource). For the reported issue at Linden Manufacturing, it does not establish the required outcome: Membership changes when a sample user department attribute changes without manual edits to every application assignment.
A new eligible group member receives the assigned entitlement and the license assignment report shows no unresolved errors. This is useful evidence for a different situation (A training application is assigned individual user licenses one account at a time and new starters routinely miss access) and action (Apply appropriate group-based licensing and monitor allocation failures where supported). For the reported issue at Linden Manufacturing, it does not establish the required outcome: Membership changes when a sample user department attribute changes without manual edits to every application assignment.
A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is useful evidence for a different situation (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) and action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources). For the reported issue at Linden Manufacturing, it does not establish the required outcome: Membership changes when a sample user department attribute changes without manual edits to every application assignment.