hardMultiple ChoiceObjective-mapped
SSCP Practice Question: A company runs containerized applications in a…
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?
⚠ Common exam trap
Mounting root as read-only prevents writes to the container filesystem but does not prevent privilege escalation; dropping capabilities directly blocks privileged operations.
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
✓
Drop all Linux capabilities from the container
Dropping all Linux capabilities from the container directly removes the ability to perform privileged operations, including privilege escalation. This is the most effective measure for preventing privilege escalation. Option A is incorrect because running as non-root does not prevent privilege escalation if the container retains capabilities. Option C is incorrect because mounting root as read-only does not prevent privilege escalation via kernel exploits or mounted volumes. Option D is incorrect because SELinux enforcing mode adds MAC but is not the most direct way to prevent privilege escalation within the container.
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
Incorrect. Running as non-root reduces risk but does not prevent privilege escalation if capabilities allow privilege escalation.
- ✓
Drop all Linux capabilities from the container
Why this is correct
Correct. Dropping all Linux capabilities removes the ability to perform privileged operations, directly preventing privilege escalation.
- ✗
Mount the container root filesystem as read-only
Why it's wrong here
Incorrect. Mounting the root filesystem as read-only prevents writes to the root filesystem but does not prevent privilege escalation through other means such as kernel exploits or mounted volumes.
- ✗
Enable SELinux enforcing mode on the host
Why it's wrong here
Incorrect. SELinux enforcing mode adds a layer of security but is not the most effective direct measure for preventing privilege escalation within the container.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
About these practice questions
This SSCP question is part of Courseiva's 920-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.