How can labels be used to create scopes or environments within a Kubernetes cluster?

How can labels be used to create scopes or environments within a Kubernetes cluster?

• A. Labels assign resource CPU limits
• B. Labels define network policies
• C. Labels can designate resources as belonging to groups such as 'development', 'testing' or 'production'
• D. Labels are used to configure node affinity only

Answer: (C)

Labels are a way to tag Kubernetes objects with meaningful metadata, like environment tags such as env=dev, env=test, or env=prod. By assigning these labels to resources (pods, deployments, services, etc.), you create a simple, flexible way to group and identify what belongs to which environment. Then, you can select and operate on just those resources using label selectors, for example kubectl commands like -l env=dev or configuring a Service or Deployment to match those labels. This makes it possible to run separate development, testing, and production scopes within the same cluster without needing separate clusters. CPU limits come from the pod spec, not labels, so that choice doesn’t describe how labels create environments. Network policies do use labels to select targets, but labeling itself is what enables the selection—not the act of defining the policy alone. Node affinity involves scheduling decisions based on labels but isn’t inherently about creating environment scopes; labels enable the selection, while affinity governs placement.

Labels are a way to tag Kubernetes objects with meaningful metadata, like environment tags such as env=dev, env=test, or env=prod. By assigning these labels to resources (pods, deployments, services, etc.), you create a simple, flexible way to group and identify what belongs to which environment. Then, you can select and operate on just those resources using label selectors, for example kubectl commands like -l env=dev or configuring a Service or Deployment to match those labels. This makes it possible to run separate development, testing, and production scopes within the same cluster without needing separate clusters.

CPU limits come from the pod spec, not labels, so that choice doesn’t describe how labels create environments. Network policies do use labels to select targets, but labeling itself is what enables the selection—not the act of defining the policy alone. Node affinity involves scheduling decisions based on labels but isn’t inherently about creating environment scopes; labels enable the selection, while affinity governs placement.