Question 950 of 997
Kubernetes FundamentalsmediumMultiple SelectObjective-mapped

Kubernetes Namespace Characteristics — Kubernetes and Cloud Native Associate Explained

This KCNA practice question tests your understanding of kubernetes fundamentals. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Which TWO of the following are characteristics of a Namespace in Kubernetes?

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

Resource names must be unique within a namespace, but can be reused across namespaces

Namespaces in Kubernetes provide a mechanism for logical grouping and scoping of resources. Two key characteristics are: (1) resource names must be unique within a namespace but can be reused across different namespaces (option C), and (2) namespaces allow multiple virtual clusters (logical clusters) within a single physical cluster (option D). While deleting a namespace does delete all its contained objects (option E), this is a consequence of namespace lifecycle management rather than a defining characteristic of what a namespace is. Network isolation is not provided by default; it requires explicit NetworkPolicy resources.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • Namespaces are required for all Kubernetes objects

    Why it's wrong here

    Incorrect. Namespaces are not required for all Kubernetes objects; some objects like nodes and persistent volumes are cluster-scoped and do not belong to a namespace.

  • Namespaces provide network isolation by default

    Why it's wrong here

    Incorrect. Namespaces do not provide network isolation by default. Network isolation is achieved through NetworkPolicy objects, not namespaces.

  • Resource names must be unique within a namespace, but can be reused across namespaces

    Why this is correct

    Correct. Kubernetes enforces unique names only within the same namespace. This allows names like 'my-app' to be reused across different namespaces (e.g., dev and prod), providing naming flexibility without collisions.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Namespaces allow multiple virtual clusters within a physical cluster

    Why this is correct

    Correct. Namespaces create separate scopes for resources, effectively allowing multiple virtual clusters within one physical cluster, enabling multi-tenancy and environment separation.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Deleting a namespace deletes all objects inside it

    Why it's wrong here

    While it is true that deleting a namespace deletes all objects inside it, this is a behavior of namespace deletion rather than a fundamental characteristic of namespaces. Since the question asks for two characteristics, options C and D are the primary ones expected.

Common exam traps

Common exam trap: answer the scenario, not the keyword

CNCF often tests the misconception that Namespaces provide built-in network isolation, but in reality, they only offer logical grouping; network segmentation requires explicit NetworkPolicy resources.

Detailed technical explanation

How to think about this question

Under the hood, Namespaces are backed by etcd key prefixes (e.g., /registry/pods/namespace-name/pod-name), which enforce name uniqueness within that prefix. In real-world scenarios, teams often use Namespaces to create virtual clusters for multi-tenancy, but without NetworkPolicies, any Pod can reach any other Pod across Namespaces via the cluster's flat network (e.g., using a CNI plugin like Calico).

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the KCNA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related KCNA practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free KCNA practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this KCNA question test?

Kubernetes Fundamentals — This question tests Kubernetes Fundamentals — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Resource names must be unique within a namespace, but can be reused across namespaces — Namespaces in Kubernetes provide a mechanism for logical grouping and scoping of resources. Two key characteristics are: (1) resource names must be unique within a namespace but can be reused across different namespaces (option C), and (2) namespaces allow multiple virtual clusters (logical clusters) within a single physical cluster (option D). While deleting a namespace does delete all its contained objects (option E), this is a consequence of namespace lifecycle management rather than a defining characteristic of what a namespace is. Network isolation is not provided by default; it requires explicit NetworkPolicy resources.

What should I do if I get this KCNA question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More KCNA practice questions

Last reviewed: Jun 30, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.