Automating Account Permissions Updates
An administrator wants to automate an account permissions update for a large number of accounts. Which of the following would best accomplish this task?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the ability to distinguish between identity governance tools (provisioning) and access control mechanisms (groups), with the trap being the confusion between managing access via groups versus automating the assignment process.
User provisioning is the correct mechanism for automating account permissions updates across large numbers of accounts, ensuring efficient identity lifecycle management.
Candidates often select Security Groups because they manage permissions, but they do not automate the update process itself; they are a static or dynamic container for access rights, not an automation engine.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
User provisioning refers to the automated creation, maintenance, management, and removal of user accounts and associated resources (such as permissions and roles) across an enterprise environment. Tools like Azure AD, Okta, or SailPoint facilitate this by using workflows to ensure that when an employee's role changes, their permissions are automatically updated without manual intervention. This directly addresses the administrator's goal of automating updates for a large number of accounts efficiently.Why the Other Options Are Wrong
Security Groups (A) are used to aggregate users and assign permissions to them, but they do not automate the process of updating those permissions; they are a method of access control, not an automation tool. Federation (B) enables Single Sign-On (SSO) and identity sharing across different domains but does not handle the granular management or automation of permission sets within a specific system. Vertical scaling (D) refers to increasing the capacity of a single server (CPU/RAM) and is unrelated to identity or access management tasks.Community Comment Notes
The community consensus strongly supports User Provisioning. As noted in the comments, 'User provisioning is the process of automating the creation, modification, management, and removal of user accounts and permissions.' Another commenter highlighted that while Federation handles SSO, it does not directly handle automated permissions updates, reinforcing the distinction between authentication federation and identity lifecycle automation.Exam Strategy
When asked about 'automating' changes to user accounts or permissions, look for terms related to Identity and Access Management (IAM) lifecycles such as 'provisioning', 'de-provisioning', or 'lifecycle management'. Do not confuse these with access control mechanisms like groups or roles, which define what access is granted but do not automate the assignment.
Frequently Asked Questions
Why isn't Federation the right answer for automating permissions?
Federation allows users to use one set of credentials to access multiple systems (SSO). It does not automate the backend process of assigning or updating specific permissions within those systems.
Can Security Groups automate permission updates?
No. Security Groups are containers that hold users. While you can assign permissions to a group, the group itself does not trigger or automate the change of those permissions based on events or roles.
Related Analysis
Practice All SY0-701 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SY0-701 Practice Test →