- A
Enabling privileged mode for containers that need host access
Why wrong: Privileged mode grants excessive permissions and should be avoided.
- B
Running containers as root
Why wrong: Running as root increases risk of privilege escalation.
- C
Running containers as a non-root user
Non-root reduces the impact of a compromise.
- D
Applying AppArmor or SELinux profiles
Mandatory access control profiles restrict container actions.
- E
Dropping all Linux capabilities and adding only required ones
Capability dropping limits kernel privileges.
Question 95 of 1,000
hardMultiple SelectObjective-mapped
CCSP A Kubernetes cluster is being hardened Practice Question
This CCSP practice question tests your understanding of a kubernetes cluster is being hardened. 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.
A Kubernetes cluster is being hardened. Which THREE measures should be implemented to restrict container capabilities and reduce the risk of privilege escalation? (Select three.)
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
✓
Running containers as a non-root user
Running as non-root user, dropping unnecessary Linux capabilities, and using AppArmor/SELinux profiles are key container security best practices. Running as root defeats isolation; privileged containers grant excessive host access.
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.
- ✗
Enabling privileged mode for containers that need host access
Why it's wrong here
Privileged mode grants excessive permissions and should be avoided.
- ✗
Running containers as root
Why it's wrong here
Running as root increases risk of privilege escalation.
- ✓
Running containers as a non-root user
Why this is correct
Non-root reduces the impact of a compromise.
Related concept
Authentication checks who the user is.
- ✓
Applying AppArmor or SELinux profiles
Why this is correct
Mandatory access control profiles restrict container actions.
Related concept
Authentication checks who the user is.
- ✓
Dropping all Linux capabilities and adding only required ones
Why this is correct
Capability dropping limits kernel privileges.
Related concept
Authentication checks who the user is.
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 developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
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 CCSP questions on access control and AAA configuration.
Related practice questions
Related CCSP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Platform and Infrastructure Security practice questions
Practise CCSP questions linked to Cloud Platform and Infrastructure Security.
Cloud Security Operations practice questions
Practise CCSP questions linked to Cloud Security Operations.
Legal, Risk, and Compliance practice questions
Practise CCSP questions linked to Legal, Risk, and Compliance.
Legal, Risk and Compliance practice questions
Practise CCSP questions linked to Legal, Risk and Compliance.
Cloud Data Security practice questions
Practise CCSP questions linked to Cloud Data Security.
Cloud Concepts, Architecture, and Design practice questions
Practise CCSP questions linked to Cloud Concepts, Architecture, and Design.
Cloud Application Security practice questions
Practise CCSP questions linked to Cloud Application Security.
Cloud Concepts, Architecture and Design practice questions
Practise CCSP questions linked to Cloud Concepts, Architecture and Design.
CCSP fundamentals practice questions
Practise CCSP questions linked to CCSP fundamentals.
CCSP scenario practice questions
Practise CCSP questions linked to CCSP scenario.
CCSP troubleshooting practice questions
Practise CCSP questions linked to CCSP troubleshooting.
Practice this exam
Start a free CCSP 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 CCSP question test?
Authentication checks who the user is.
What is the correct answer to this question?
The correct answer is: Running containers as a non-root user — Running as non-root user, dropping unnecessary Linux capabilities, and using AppArmor/SELinux profiles are key container security best practices. Running as root defeats isolation; privileged containers grant excessive host access.
What should I do if I get this CCSP 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 CCSP questions on access control and AAA configuration.
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: Jul 4, 2026
This CCSP 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 CCSP 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.