- A
The container is trying to write to a read-only filesystem
Why wrong: If the filesystem is read-only, the container would fail with a different error (e.g., 'Read-only file system'). The scenario does not mention readOnlyRootFilesystem.
- B
The container is trying to set capabilities using setcap
Setting capabilities requires privilege escalation, which is disabled. This will cause the operation to fail and the container to crash.
- C
The container is missing the NET_ADMIN capability
Why wrong: Missing a capability would not cause a crash; the container would simply fail to perform the privileged operation and might log an error, but it would not necessarily crash.
- D
The container is trying to bind to a privileged port (<1024) as non-root
Why wrong: Binding to a privileged port requires CAP_NET_BIND_SERVICE, which may still be allowed if the container has that capability initially. It's not the most likely cause.
CKS Minimize Microservice Vulnerabilities Practice Question
This CKS practice question tests your understanding of minimize microservice vulnerabilities. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A pod is failing with 'CrashLoopBackOff'. The pod's securityContext includes 'allowPrivilegeEscalation: false'. The container image is built with a default user of root and attempts to change capabilities. What is the most likely cause of the crash?
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.
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
The container is trying to set capabilities using setcap
Option C is correct. With allowPrivilegeEscalation: false, the container cannot gain additional privileges beyond its initial capabilities. If the container tries to set capabilities (e.g., via setcap), it will fail and crash. Options A and B are possible but less likely given the symptom. Option D is unrelated.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
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 container is trying to write to a read-only filesystem
Why it's wrong here
If the filesystem is read-only, the container would fail with a different error (e.g., 'Read-only file system'). The scenario does not mention readOnlyRootFilesystem.
- ✓
The container is trying to set capabilities using setcap
Why this is correct
Setting capabilities requires privilege escalation, which is disabled. This will cause the operation to fail and the container to crash.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Authentication checks who the user is.
- ✗
The container is missing the NET_ADMIN capability
Why it's wrong here
Missing a capability would not cause a crash; the container would simply fail to perform the privileged operation and might log an error, but it would not necessarily crash.
- ✗
The container is trying to bind to a privileged port (<1024) as non-root
Why it's wrong here
Binding to a privileged port requires CAP_NET_BIND_SERVICE, which may still be allowed if the container has that capability initially. It's not the most likely cause.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Trap categories for this question
Scenario analysis trap
If the filesystem is read-only, the container would fail with a different error (e.g., 'Read-only file system'). The scenario does not mention readOnlyRootFilesystem.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
- Authentication checks who the user is.
- Authorization controls what the user is allowed to do after login.
- Privilege levels affect access to EXEC and configuration commands.
- AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
- Do not assume successful login means full administrative access.
- Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
- Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related CKS questions on access control and AAA configuration.
- →
Minimize Microservice Vulnerabilities — study guide chapter
Learn the concepts, then practise the questions
- →
Minimize Microservice Vulnerabilities practice questions
Targeted practice on this topic area only
- →
All CKS questions
997 questions across all exam domains
- →
Certified Kubernetes Security Specialist CKS study guide
Full concept coverage aligned to exam objectives
- →
CKS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Cluster Setup and Hardening practice questions
Practise CKS questions linked to Cluster Setup and Hardening.
System Hardening practice questions
Practise CKS questions linked to System Hardening.
Minimize Microservice Vulnerabilities practice questions
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Supply Chain Security practice questions
Practise CKS questions linked to Supply Chain Security.
Monitoring, Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Cluster Setup practice questions
Practise CKS questions linked to Cluster Setup.
Cluster Hardening practice questions
Practise CKS questions linked to Cluster Hardening.
CKS fundamentals practice questions
Practise CKS questions linked to CKS fundamentals.
CKS scenario practice questions
Practise CKS questions linked to CKS scenario.
CKS troubleshooting practice questions
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Start a free CKS 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 CKS question test?
Minimize Microservice Vulnerabilities — This question tests Minimize Microservice Vulnerabilities — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: The container is trying to set capabilities using setcap — Option C is correct. With allowPrivilegeEscalation: false, the container cannot gain additional privileges beyond its initial capabilities. If the container tries to set capabilities (e.g., via setcap), it will fail and crash. Options A and B are possible but less likely given the symptom. Option D is unrelated.
What should I do if I get this CKS question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related CKS questions on access control and AAA configuration.
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?
Authentication checks who the user is.
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 →
Last reviewed: Jun 21, 2026
This CKS 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 CKS 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.