The answer is to mount the container root filesystem as read-only. This configuration is most effective because it directly enforces a read-only root filesystem, preventing any process—even one that has escalated privileges—from writing malicious files or altering system binaries within the container. By blocking writes to the container’s own filesystem, you limit the blast radius of a compromise, as an attacker cannot persist changes or install tools. On the Systems Security Certified Practitioner SSCP exam, this concept tests your understanding of container security fundamentals and the principle of least privilege; a common trap is confusing user-level restrictions like running as non-root with filesystem-level controls. Remember that dropping capabilities or using SELinux adds defense in depth, but only a read-only filesystem stops write access at the storage layer. Memory tip: “Read-only roots block the roots of attack.”
SSCP Systems and Application Security Practice Question
This SSCP practice question tests your understanding of systems and application security. 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 company runs containerized applications in a Kubernetes cluster. They need to ensure that containers run with the least privilege and cannot escalate privileges. Which configuration change is MOST effective?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "least"
Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Mount the container root filesystem as read-only
Option D is correct because setting a read-only root filesystem prevents container from writing to its own filesystem, limiting damage from compromise. Option A is wrong because running as non-root is important but does not prevent privilege escalation if capabilities allow. Option B is wrong because dropping all capabilities reduces risk but does not prevent writes to root filesystem. Option C is wrong because SELinux enforcing mode adds a layer but is not directly about privilege escalation in containers.
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.
✗
Set the container to run as non-root user
Why it's wrong here
Non-root is good but if binary has setuid or capabilities, escalation is possible.
✗
Drop all Linux capabilities from the container
Why it's wrong here
Drops capabilities but does not prevent writes to writable filesystems.
✓
Mount the container root filesystem as read-only
Why this is correct
Prevents writing to the container's filesystem, limiting impact of a compromise.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Authentication checks who the user is.
✗
Enable SELinux enforcing mode on the host
Why it's wrong here
Provides mandatory access control but not specifically for privilege escalation.
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.
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 SOC analyst notices unusual lateral movement in the network at 2 AM. The IR playbook dictates: identify and contain (isolate the affected machine), then eradicate (remove the malware), then recover (restore from backup), then document. Skipping containment before eradication risks the attacker regaining access. Questions like this test the sequence and rationale of incident response phases.
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 SSCP questions on access control and AAA configuration.
Systems and Application Security — This question tests Systems and Application Security — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Mount the container root filesystem as read-only — Option D is correct because setting a read-only root filesystem prevents container from writing to its own filesystem, limiting damage from compromise. Option A is wrong because running as non-root is important but does not prevent privilege escalation if capabilities allow. Option B is wrong because dropping all capabilities reduces risk but does not prevent writes to root filesystem. Option C is wrong because SELinux enforcing mode adds a layer but is not directly about privilege escalation in containers.
What should I do if I get this SSCP 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 SSCP questions on access control and AAA configuration.
Are there clue words in this question I should notice?
Yes — watch for: "least". You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
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 →
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 SSCP practice question is part of Courseiva's free ISC2 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 SSCP 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.