HR ticket-only provisioning for a large city workforce causes multi-day delays and frequent wrong-role assignments. Which improvement best addresses reliability while retaining governance?
Select an answer to reveal the explanation.
Short Explanation
Hand-built tickets for every hire are like cutting metal keys one at a time for a skyscraper. Wire HRIS to IAM with approvals and an audit trail—faster onboarding, fewer wrong doors, still governed.
Full Explanation
Reliable municipal provisioning at scale needs automated joiner/mover/leaver workflows fed by an authoritative HRIS, with policy-driven role assignment, manager approvals for sensitive entitlements, and auditable tickets or logs. Automation cuts multi-day delays and wrong-role mistakes that plague HR-ticket-only processes for large city workforces, while governance gates preserve separation of duties and accountability. The goal is timely, consistent lifecycle execution—not speed without control.
Letting each department create local AD accounts without central review restores the wild-west pattern automation was meant to end and fragments identity. Emailing passwords in bulk spreadsheets accelerates day-one access by broadcasting secrets and destroying confidentiality of initial credentials. Turning off access reviews because automation exists assumes provisioning is always perfect; reviews remain necessary for exceptions, role drift, and orphan detection.
Exam caveat: automation and reviews are complementary controls in Domain 5 lifecycle design. Operational check: integrate hire/transfer/terminate events to the IAM engine with SLAs, require dual control for privileged roles, monitor failed provisioning jobs, and keep periodic recertification on the calendar even after automation goes live.