Question 417 of 991
Application Environment, Configuration and SecuritymediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is request: 200m and limit: 500m. This occurs because a LimitRange in namespace 'ns' defines default CPU request and limit values that are automatically injected by the LimitRanger admission controller when a pod is created without specifying any CPU resources. The admission plugin intercepts the pod creation request and applies the defaults from the LimitRange, ensuring every container has resource constraints even if the user omits them. On the CKAD exam, this tests your understanding of how LimitRange defaults interact with pod specifications—a common trap is assuming that a pod without resource requests or limits will run unrestricted, but the LimitRange overrides that behavior. Remember that LimitRange defaults only apply when the container’s resource field is completely absent; if you set only one of request or limit, the default for the other is not applied. A useful memory tip: “No spec, get default—LimitRange fills the gap.”

CKAD Practice Question: Application Environment, Configuration and Security

This CKAD practice question tests your understanding of application environment, configuration and security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.

You have a LimitRange in namespace 'ns' that sets default limits.cpu to 500m and default requests.cpu to 200m. You create a pod without specifying any CPU resources. What CPU values will be applied to the container?

Question 1mediummultiple choice
Full question →

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

request: 200m, limit: 500m

When a LimitRange is configured in a namespace with default CPU limits and requests, any pod created without specifying CPU resources will have those defaults injected by the admission controller. The LimitRange sets default limits.cpu to 500m and default requests.cpu to 200m, so the container will receive request: 200m and limit: 500m. This is enforced by the LimitRanger admission plugin during pod creation.

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.

  • The pod will be rejected by the admission controller

    Why it's wrong here

    Incorrect. LimitRange does not reject pods that lack resource specs; it applies defaults.

  • request: 200m, limit: 500m

    Why this is correct

    Correct. LimitRange defaults apply to containers that don't specify resource requirements.

    Related concept

    Read the scenario before looking for a memorised answer.

  • request: 0, limit: 0 (no limits enforced)

    Why it's wrong here

    Incorrect. LimitRange will apply defaults, so there will be values.

  • request: 500m, limit: 500m

    Why it's wrong here

    Incorrect. The default request is 200m, not 500m.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume a pod without resource specs will be rejected or have no limits, but the LimitRange admission controller silently applies defaults, making option B correct.

Detailed technical explanation

How to think about this question

The LimitRanger admission plugin intercepts pod creation requests and applies default resource requirements from the LimitRange object if the container does not specify them. This is part of Kubernetes' admission control chain, which runs before the pod is persisted in etcd. In real-world scenarios, this ensures that teams without explicit resource specifications still have sensible defaults, preventing resource starvation or overcommitment in the cluster.

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 CKAD 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 CKAD 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 CKAD 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 CKAD question test?

Application Environment, Configuration and Security — This question tests Application Environment, Configuration and Security — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: request: 200m, limit: 500m — When a LimitRange is configured in a namespace with default CPU limits and requests, any pod created without specifying CPU resources will have those defaults injected by the admission controller. The LimitRange sets default limits.cpu to 500m and default requests.cpu to 200m, so the container will receive request: 200m and limit: 500m. This is enforced by the LimitRanger admission plugin during pod creation.

What should I do if I get this CKAD 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

Last reviewed: Jun 25, 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 CKAD 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 CKAD exam.