Your company is migrating its document management system to a cloud-based service. Employees' access to documents will be governed by their job functions. One employee's role requires them to review, comment on, and suggest edits to documents but prohibits them from directly modifying content or accessing document version history. How should the cloud administrator configure access for this employee?
You selected this option
Assign a role that includes permissions for document viewing, commenting, and suggesting edits without the ability to make direct changes or view the document history.
You selected this option
Give 'Commenter' access and modify the role to allow for editing, not considering history permissions.
You selected this option
Grant the employee 'Editor' rights to ensure they can review and suggest changes.
You selected this option
Provide 'Viewer' access to maintain the highest level of document integrity and security.
In role-based access control, it's important to match the role permissions with the specific job functions required by the user. The role that allows document viewing, commenting, and suggesting—without editing capabilities or access to the document version history—best fits the user's job function. The incorrect options either provide access that is broader than necessary, potentially violating the principle of least privilege, or don't provide all the necessary job-function permissions.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is role-based access control (RBAC)?
Open an interactive chat with Bash
What are the benefits of implementing the principle of least privilege?
Open an interactive chat with Bash
How do access permissions affect document management in the cloud?