Question 51 — AB-650 Case Study Set
Paideffort's intended permission model is stored as:
workflows:
userProvisioning:
operation: create-update-delete-users
scope: User.ReadWrite.All
quarterlyAudit:
operation: export-users
scope: User.Read.All
officeMembership:
operation: modify-group-membership
scope: GroupMember.ReadWrite.All
regionalDelegation:
operation: manage-administrative-units
scope: AdministrativeUnit.ReadWrite.All
An engineer proposes replacing every scope in this configuration with Directory.ReadWrite.All to simplify authentication across all automation. What is the best architecture decision? (Select one answer)
Retain the task-specific scopes because Paideffort's workflows have distinct permission requirements and the broader directory scope would weaken least-privilege separation.
Replace all scopes because a single directory-wide scope reduces script complexity without changing Paideffort's security exposure.
Replace only
User.Read.Allbecause a read-only audit should use a write permission in case administrators later add remediation.Merge the four workflows into one script and request every available Graph scope so future identity requirements do not require permission changes.
Correct answers
Retain the task-specific scopes because Paideffort's workflows have distinct permission requirements and the broader directory scope would weaken least-privilege separation.
Explanations
Correct Answer:
Retain the task-specific scopes because Paideffort's workflows have distinct permission requirements and the broader directory scope would weaken least-privilege separation.
Explanation:
Paideffort deliberately separates user lifecycle management, read-only auditing, group membership, and administrative-unit management. The YAML design grants each workflow a scope aligned with the resource it changes or reads. Replacing all of them with Directory.ReadWrite.All would simplify the permission list at the cost of giving each workflow substantially more authority than its function requires.
Wrong Answers:
Replace all scopes because a single directory-wide scope reduces script complexity without changing Paideffort's security exposure.
The change materially increases security exposure because workflows such as the read-only audit would receive directory-wide write capability that they do not need.
Replace only User.Read.All because a read-only audit should use a write permission in case administrators later add remediation.
Paideffort specifically requires the audit process to remain read-only. Granting speculative future write access violates that control.
Merge the four workflows into one script and request every available Graph scope so future identity requirements do not require permission changes.
This maximizes privilege rather than aligning authorization with defined operations. It also undermines Paideffort's ability to govern and audit each workflow independently.