What is a valid use case for the No Access role?
A.
An administrator wants to revoke permissions on an object that would otherwise be propagated.
B.
An administrator wants to allow the state and details of an object to be viewed, but provide no other access.
C.
An administrator wants to allow only the status of an object to be viewed, but provide no other access.
D.
An administrator wants to prevent a user from launching the vSphere Client.
C.
An administrator wants to revoke permissions on an object that would otherwise be propagated
Is the correct answer. All others didn’t make sense.
0
0
a is correct
http://pubs.vmware.com/vsphere-4-esxi-installable-vcenter/index.jsp?topic=/com.vmware.vsphere.esxi_server_config.doc_41/esx_server_config/authentication_and_user_management/c_no_access.html
Assigning the No Access Role
Users assigned the No Access role for an object cannot view or change the object in any way. New users and groups are assigned this role by default. You can change the role on an object-by-object basis.
The root user and vpxuser permissions are the only users not assigned the No Access role by default. Instead, they are assigned the Administrator role. You can delete the root user’s permissions altogether or change its role to No Access as long as you first create a replacement permission at the root level with the Administrator role and associate this role with a different user.
0
0