CKAD Application Observability and Maintenance Practice Question
This CKAD practice question tests your understanding of application observability and maintenance. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
Exhibit
Refer to the exhibit.
$ kubectl logs myapp-6b4d9f8c7d-abcde
Error: listening on :8080: bind: address already in use
$ kubectl describe pod myapp-6b4d9f8c7d-abcde | grep -A5 Last State
Last State: Terminated
Reason: Error
Exit Code: 1
Message: listening on :8080: bind: address already in use
The Pod 'myapp' is in CrashLoopBackOff. Based on the exhibit, what is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Refer to the exhibit.
$ kubectl logs myapp-6b4d9f8c7d-abcde
Error: listening on :8080: bind: address already in use
$ kubectl describe pod myapp-6b4d9f8c7d-abcde | grep -A5 Last State
Last State: Terminated
Reason: Error
Exit Code: 1
Message: listening on :8080: bind: address already in use
A
The init container failed to complete.
Why wrong: The log is from the main container, not an init container.
B
The readiness probe is misconfigured.
Why wrong: Readiness probe misconfiguration would not cause this error.
C
The container is trying to bind to a port already used by a sidecar or previous instance.
The error indicates port conflict.
D
The liveness probe is failing and restarting the container.
Why wrong: Liveness probe failure would not produce 'address already in use'.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The container is trying to bind to a port already used by a sidecar or previous instance.
The Pod is in CrashLoopBackOff, which indicates the container repeatedly crashes. The most likely cause is that the container is trying to bind to a port already in use by a sidecar or a previous instance of the same container that hasn't fully terminated. This is a common scenario when a sidecar container (e.g., a logging proxy) binds to the same port, or when the container's port is not released quickly enough after a restart, leading to an immediate crash on startup.
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 init container failed to complete.
Why it's wrong here
The log is from the main container, not an init container.
✗
The readiness probe is misconfigured.
Why it's wrong here
Readiness probe misconfiguration would not cause this error.
✓
The container is trying to bind to a port already used by a sidecar or previous instance.
Why this is correct
The error indicates port conflict.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The liveness probe is failing and restarting the container.
Why it's wrong here
Liveness probe failure would not produce 'address already in use'.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume CrashLoopBackOff is always caused by a failing liveness probe (Option D), but they overlook that the container must actually start and run for the liveness probe to be checked; if the container crashes immediately on startup (e.g., due to port conflict), the liveness probe never even runs, and the root cause is a startup failure, not a probe failure.
Detailed technical explanation
How to think about this question
When a container tries to bind to a port (e.g., via net.Listen or socket() syscall), the kernel returns EADDRINUSE if the port is already in use by another process in the same network namespace. In Kubernetes, sidecar containers share the same network namespace (Pod-level), so if a sidecar (e.g., Envoy, Istio proxy) binds to the same port, the main container will fail immediately. Additionally, if a previous instance of the container hasn't fully terminated (e.g., due to lingering TIME_WAIT state on the socket), the new container may fail to bind, causing a crash loop. This is a common real-world issue when migrating from a single-container Pod to a multi-container Pod without adjusting port assignments.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKAD question in full detail.
Application Observability and Maintenance — This question tests Application Observability and Maintenance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The container is trying to bind to a port already used by a sidecar or previous instance. — The Pod is in CrashLoopBackOff, which indicates the container repeatedly crashes. The most likely cause is that the container is trying to bind to a port already in use by a sidecar or a previous instance of the same container that hasn't fully terminated. This is a common scenario when a sidecar container (e.g., a logging proxy) binds to the same port, or when the container's port is not released quickly enough after a restart, leading to an immediate crash on startup.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.
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.
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.
Sign in to join the discussion.