Required authorizations before creating user identities are part of which process?

• A. Access Revocation
• B. Subgroups
• C. Approval Processes
• D. Identity Life Cycle

Answer: (C)

The main idea being tested is governance around provisioning, specifically the need for formal sign-off before a new identity is created. Requiring authorizations before creating user identities ensures that requests are legitimate, align with policy, and have the appropriate approvals from managers or owners. It creates an auditable trail and helps enforce least privilege by preventing unnecessary or inappropriate accounts from being provisioned.

This step acts as the approval workflow that gates the provisioning process. Without it, accounts could be created without proper oversight, increasing risk of misconfigurations or privilege creep. While the broader Identity Life Cycle covers provisioning, maintenance, and deprovisioning, the explicit gate that ensures someone approves the creation of the identity is the approval process. Access revocation and subgroups address other aspects (removing access and grouping users), so they don’t fit as the mechanism for pre-create authorization.