2V0-622 · Question #3
An administrator with global administrator privileges creates a custom role but fails to assign any privileges to it. Which two privileges would the custom role have? (Choose two.)
The correct answer is A. System.View B. System.Anonymous. vCenter automatically assigns the System.Anonymous and System.View system privileges to every role, including custom roles with no manually assigned privileges.
Question
An administrator with global administrator privileges creates a custom role but fails to assign any privileges to it. Which two privileges would the custom role have? (Choose two.)
Options
- ASystem.View
- BSystem.Anonymous
- CSystem.User
- DSystem.ReadOnly
How the community answered
(54 responses)- A85% (46)
- C11% (6)
- D4% (2)
Why each option
vCenter automatically assigns the System.Anonymous and System.View system privileges to every role, including custom roles with no manually assigned privileges.
System.View is one of the two mandatory system privileges that vCenter automatically adds to all roles, allowing the holder to view basic object information in the inventory.
System.Anonymous is the other mandatory system privilege automatically present on all roles, representing the minimum level of access for any unauthenticated or custom role in vCenter.
System.User is granted implicitly to authenticated sessions but is not automatically added as a privilege to custom role definitions in vCenter.
System.ReadOnly is not automatically assigned to custom roles; it must be explicitly added or is only present on the Read-Only system role.
Concept tested: Automatic system privileges on vCenter custom roles
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-FEAB5DF5-F7A2-412D-BF3D-7420A355AE8F.html
Topics
Community Discussion
No community discussion yet for this question.