KCNA Kubernetes Fundamentals Practice Question
What is the primary purpose of a Namespace in Kubernetes?
⚠ Common exam trap
Candidates often confuse Namespaces with other cluster-level constructs like ResourceQuotas or NetworkPolicies, assuming Namespaces directly enforce limits or rules, when in fact Namespaces only provide the scope for names and isolation, while other objects (like ResourceQuotas, NetworkPolicies, and RBAC) are applied to that scope.
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
✓
To isolate resources and provide a scope for names
Namespaces in Kubernetes provide a mechanism for isolating groups of resources within a single cluster. They create separate scopes for resource names, meaning that resource names (like Pods or Services) only need to be unique within a Namespace, not across the entire cluster. This allows multiple teams or projects to share a cluster without naming conflicts, and it also enables cluster administrators to apply policies (like ResourceQuotas) and network policies at the Namespace level.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To set resource quotas for the entire cluster
Why it's wrong here
Resource quotas can be applied per namespace, but that is not the primary purpose.
- ✗
To define network policies for pods
Why it's wrong here
Network policies define network rules, not the scope of resource names.
- ✗
To manage node affinity rules
Why it's wrong here
Node affinity is configured in pod specs, not via namespaces.
- ✓
To isolate resources and provide a scope for names
Why this is correct
Namespaces partition resources into logically named groups.
Go deeper
Related to this question
Learn chapter
Kubernetes Overview and Core Components
Key term
Namespaces
A Namespace in Kubernetes is a virtual cluster within a physical cluster that allows you to organize and isolate resources, like an apartment building with separate units for different tenants.
Key term
ReplicaSet and Replication
A ReplicaSet ensures a specified number of identical pod instances are running at all times in Kubernetes, using replication to maintain availability and stability.
About these practice questions
This KCNA question is part of Courseiva's 833-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 →
Same concept, more angles
2 more ways this is tested on KCNA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. What is the purpose of a Namespace in Kubernetes?
easy- A.To assign IP addresses to services
- B.To limit the number of pods that can be created
- ✓ C.To logically isolate resources like pods and services
- D.To provide DNS names for pods
Why C: Namespaces in Kubernetes provide a mechanism for logically isolating resources such as Pods, Services, and Deployments within a cluster. They enable multiple virtual clusters to coexist on the same physical cluster, allowing for resource scoping, access control, and organization by team or environment (e.g., dev, staging, prod). This isolation is fundamental to multi-tenancy and resource management in Kubernetes.
Variation 2. Which TWO are valid reasons to use a Namespace in Kubernetes?
medium- ✓ A.To enforce network policies that restrict traffic between Pods in different Namespaces.
- B.To reduce the number of API calls to the control plane.
- ✓ C.To isolate resources and prevent naming collisions between different teams.
- D.To improve application performance by reducing latency.
- E.To store environment variables for containers.
Why A: Kubernetes NetworkPolicies are namespace-scoped resources that can restrict ingress and egress traffic between Pods in different Namespaces. By default, all Pods can communicate across Namespaces, but applying a NetworkPolicy with a podSelector and namespaceSelector allows you to enforce isolation. Option C is correct because Namespaces provide a logical boundary for resource names, preventing naming collisions when multiple teams or projects deploy objects with the same name within the same cluster.
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.