RBAC in vCenter Server stands for Role-Based Access Control.

RBAC in vCenter Server stands for Role-Based Access Control.

• A. Role-Based Access Control
• B. Remote Backed Access Center
• C. Resource-Based Access Control
• D. Role-Backed Administrative Console

Answer: (A)

RBAC stands for Role-Based Access Control. The idea is to manage who can do what by assigning defined roles to users or groups, rather than granting permissions for each action individually. In vCenter Server, you create roles that are sets of privileges (such as operations on VMs, hosts, or datastores) and apply those roles at a chosen scope—like a datacenter, cluster, resource pool, or a specific object. This approach makes access control scalable and precise: a user can be given enough privileges to perform their job without exposing sensitive operations. The other options don’t fit because they describe terms that aren’t used for RBAC in vCenter: they either suggest different phrases or models (such as a nonstandard term, or a resource-based or administrative-console variant) that do not match the established meaning of RBAC.

RBAC stands for Role-Based Access Control. The idea is to manage who can do what by assigning defined roles to users or groups, rather than granting permissions for each action individually. In vCenter Server, you create roles that are sets of privileges (such as operations on VMs, hosts, or datastores) and apply those roles at a chosen scope—like a datacenter, cluster, resource pool, or a specific object. This approach makes access control scalable and precise: a user can be given enough privileges to perform their job without exposing sensitive operations.

The other options don’t fit because they describe terms that aren’t used for RBAC in vCenter: they either suggest different phrases or models (such as a nonstandard term, or a resource-based or administrative-console variant) that do not match the established meaning of RBAC.