Which of the following are vCenter Server System Roles that cannot be modified?

The vCenter Server System Roles that cannot be modified include the No Access Role, Read-only Role, and No Cryptography Administrator Role. These roles are defined with specific permissions that cannot be altered or customized.

The No Access Role is critical as it explicitly denies any access to the resources within vCenter Server, serving as a fundamental permission boundary. The Read-only Role allows users to view the inventory and performance data without making any changes, which is essential for maintaining the integrity of the environment while allowing for oversight and monitoring.

The No Cryptography Administrator Role is also rigid in its definition, providing specific permissions related to cryptography settings without allowing changes that could compromise security.

Collectively, these roles serve essential functions within vCenter Server’s permission model, ensuring that certain access levels are consistently enforced. Since no modifications can be made to these predefined roles, they stand as solid fixtures within the permissions framework of vCenter Server, maintaining both security and operational integrity.