Courseiva
Kubernetes Fundamentals →mediumMultiple Choice

KCNA Kubernetes Fundamentals Practice Question

You want to isolate a team's workloads within a Kubernetes cluster so that they cannot see or access resources from other teams. Which feature should you use?

⚠ Common exam trap

The trap is that candidates confuse labels/selectors (which are for organization and routing within the same namespace) with namespaces (which provide true isolation and multi-tenancy across the cluster). This leads them to select Option B, thinking selectors control visibility, but they only filter resources within a namespace.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Namespaces

Namespaces are the Kubernetes abstraction that provides a logical partition of the cluster, enabling multi-tenancy by isolating workloads, resources, and access controls. By default, RBAC policies and network policies can be scoped to a namespace, preventing teams from seeing or accessing resources in other namespaces.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Annotations

    Why it's wrong here

    Annotations attach non-identifying metadata to objects; they enforce no access boundaries, so teams still see and reach each other's resources. They are tempting because they label workloads for tooling and cost reporting. Namespaces, combined with RBAC and NetworkPolicy, provide the isolation the scenario requires.

  • ✗

    Labels and selectors

    Why it's wrong here

    Labels and selectors only group and query objects; they enforce no access boundary, so one team's pods can still reach another's. They are tempting because NetworkPolicy selectors rely on labels, but isolation itself requires NetworkPolicy objects, which labels merely target rather than implement.

  • ✗

    Resource quotas

    Why it's wrong here

    Resource quotas cap aggregate CPU, memory and object counts per namespace; they do not restrict network or API visibility between teams. They are tempting because namespaces already scope resources, but quotas address consumption limits, whereas NetworkPolicy supplies the actual isolation the scenario requires.

  • ✓

    Namespaces

    Why this is correct

    Namespaces partition a single cluster into logically isolated virtual clusters, scoping namespaced resources and their names so a team's workloads cannot see or access another team's objects. This satisfies the stem's isolation requirement without provisioning separate clusters, though network policies are still needed to restrict cross-namespace traffic.

Quick reference

Access Control Model Comparison

ModelAcronymWho Controls Access?Best For
Discretionary Access ControlDACResource ownerSmall teams, file shares
Mandatory Access ControlMACSystem / security labelsClassified govt / military
Role-Based Access ControlRBACAdministrator (via roles)Enterprise environments
Attribute-Based Access ControlABACPolicy engine (user + resource attributes)Fine-grained, dynamic policies
Rule-Based Access ControlRuBACSystem rules / ACLsFirewall rules, network ACLs

About these practice questions

This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This KCNA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the KCNA exam.