Both of these resources are cluster-wide objects:
PersistentVolumes (PVs) are storage resources provisioned by an administrator that exist at the cluster level. They aren't bound to any specific namespace and can be claimed by PersistentVolumeClaims (PVCs) from any namespace. This cluster-wide design allows for centralized storage management across the entire Kubernetes cluster.
ClusterRoles are part of Kubernetes' RBAC (Role-Based Access Control) system and define permissions at the cluster level. Unlike regular Roles that are namespace-specific, ClusterRoles apply across all namespaces. They're used to grant permissions for cluster-wide resources or for resources across all namespaces.
#######
A) Nodes and Deployments
B) Namespaces and NetworkPolicies
Namespaces are cluster-wide objects (correct) - ironically, the namespaces themselves are cluster-wide resources even though they're used to scope other resources
NetworkPolicies are namespace-scoped objects (incorrect) - they control network traffic within specific namespaces
D) Secrets and CustomResourceDefinitions
Secrets are namespace-scoped objects (incorrect) - they store sensitive information within a specific namespace
CustomResourceDefinitions (CRDs) are cluster-wide objects (correct) - they extend the Kubernetes API at the cluster level