ITGSS Certified DevOps Engineer Practice Test 2025 - Free DevOps Practice Questions and Exam Preparation Guide

In the Role-Based Access Control (RBAC) model, the concept of resource types is paired with verbs to define the actions that can be performed on those resources. While all the resources mentioned in the choices—Pods, Services, Deployments—are indeed associated with specific verbs like 'get', 'list', 'create', and 'delete', Namespaces stand out as being a different case.

Namespaces are more of a logical partitioning mechanism within a Kubernetes cluster rather than a core resource type in the way the others are. While you can perform operations like creating or deleting a namespace, it doesn't lend itself to the same set of interactions that are typical with Pods, Services, and Deployments. Those resource types have a more extensive and diverse set of verbs associated with specific actions you would typically perform.

Thus, while you can use verbs in context with namespaces (such as creating or deleting a namespace), the range and nature of actions you can use with namespaces do not parallel those associated with the other resource types in a way that establishes a typical pairing in the RBAC model. This distinction makes it clear why namespaces are not conventionally viewed in the same light when discussing the RBAC model's structure.