Question 850
A bulk script disables accounts with a wildcard matching similar surnames and accidentally targets active employees. What should the administrator do FIRST to correct the problem?
Explanation
Correct Answer
The deciding issue is display names are not unique stable identifiers for destructive directory automation. The action 'Use immutable object IDs and preview the exact affected identity set before bulk account modifications.' targets that issue rather than a neighboring Microsoft 365 workload. Confirm it by checking: A controlled dry run identifies only the approved offboarding objects and leaves a namesake active.
Incorrect Answers
Creating user principals for address-only contacts introduces needless identity and license exposure. The problem described here is that display names are not unique stable identifiers for destructive directory automation.
An assigned SKU without the intended enabled service plan can leave a workload unavailable. The problem described here is that display names are not unique stable identifiers for destructive directory automation.
Group visibility and membership determine broad collaboration exposure across related workloads. The problem described here is that display names are not unique stable identifiers for destructive directory automation.