hardMultiple ChoiceObjective-mapped
200-901 Practice Question: During a security audit of a microservices…
During a security audit of a microservices application deployed on Cisco Container Platform, the auditor discovers that some containers are running with privileged access. The development team argues that certain containers need to modify kernel parameters. Which security best practice should be recommended to minimize risk while allowing necessary kernel adjustments?
⚠ Common exam trap
Cisco often tests the distinction between privileged mode and individual capabilities, where candidates mistakenly think setting `privileged: false` is required alongside capability addition, or that running as root is necessary for kernel modifications.
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
✓
Set the container security context to add only the necessary Linux capabilities, e.g., CAP_SYS_ADMIN
It follows the principle of least privilege by granting only the specific Linux capability (CAP_SYS_ADMIN) needed to modify kernel parameters, rather than full privileged access. In Kubernetes (used by Cisco Container Platform), a security context with `capabilities.add: ['SYS_ADMIN']` allows the container to perform privileged operations like sysctl modifications without exposing the host or other containers to the broader risks of privileged mode.
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 security context to add only the necessary Linux capabilities, e.g., CAP_SYS_ADMIN
Why this is correct
This grants only the required capabilities, reducing the attack surface compared to privileged mode.
- ✗
Set the container to privileged: false and add the SYS_ADMIN capability only for containers that need it
Why it's wrong here
Setting privileged: false is redundant with adding capabilities; the correct approach is to use capabilities without privileged flag.
- ✗
Run the container as root user but remove the CAP_SYS_ADMIN capability
Why it's wrong here
Removing CAP_SYS_ADMIN would prevent kernel parameter changes, and running as root is still dangerous.
- ✗
Drop all Linux capabilities and run the container as a non-root user
Why it's wrong here
Dropping all capabilities would prevent the required kernel modifications.
Go deeper
Related to this question
About these practice questions
One of 989 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco 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 200-901 exam.