How do you grant a user permissions to manage resources within a project using RBAC?

• A. Bind the user to an existing ServiceAccount with a RoleBinding.
• B. Create a Role or ClusterRole and bind it to the user with a RoleBinding (for a namespace) or ClusterRoleBinding (cluster-wide) with oc.
• C. Use a SecurityContextConstraint to assign admin rights.
• D. Use a ConfigMap to store permissions.

Answer: (B)

RBAC grants access by linking what a user can do with who they are. To let a user manage resources in a project, you define a Role that lists the allowed actions on the resources within that namespace (or a ClusterRole for cluster-wide permissions), and then attach that role to the user using a RoleBinding in the namespace (or a ClusterRoleBinding for cluster-wide access). This is the standard way to give project-scoped permissions in OpenShift: create the role with the needed rules and bind it to the user in the project, or use a cluster-wide role bound at the cluster level if broader access is required. Using a SecurityContextConstraints is not for general RBAC permissions, and a ConfigMap is just for storing configuration data, not access control.