- A
Using RBAC to restrict service account permissions
Why wrong: RBAC controls what actions service accounts can perform, but does not directly limit the blast radius of a compromised container.
- B
Implementing Kubernetes network policies to restrict pod-to-pod communication
Network policies limit which pods can communicate, containing potential lateral movement.
- C
Performing regular container image scanning for vulnerabilities
Why wrong: Image scanning identifies vulnerabilities but does not limit the blast radius once a container is compromised.
- D
Applying seccomp profiles to limit system call availability
Seccomp restricts the system calls a container can make, reducing the attack surface.
- E
Enforcing Pod Security Standards (PSS) such as 'restricted' policy
PSS can prevent containers from running with elevated privileges, reducing impact of compromise.
CAS-004 Security Architecture Practice Question
This CAS-004 practice question tests your understanding of security architecture. 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.
An organization is hardening its Kubernetes cluster. Which THREE of the following are effective controls to limit the blast radius of a compromised container?
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
Implementing Kubernetes network policies to restrict pod-to-pod communication
Network policies restrict communication between pods, limiting lateral movement. Seccomp profiles restrict system calls, reducing attack surface. Pod Security Standards (PSS) enforce security contexts like not running as root. RBAC controls user access, not container-to-container. Image scanning identifies vulnerabilities but does not limit blast radius.
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.
- ✗
Using RBAC to restrict service account permissions
Why it's wrong here
RBAC controls what actions service accounts can perform, but does not directly limit the blast radius of a compromised container.
- ✓
Implementing Kubernetes network policies to restrict pod-to-pod communication
Why this is correct
Network policies limit which pods can communicate, containing potential lateral movement.
Related concept
Authentication checks who the user is.
- ✗
Performing regular container image scanning for vulnerabilities
Why it's wrong here
Image scanning identifies vulnerabilities but does not limit the blast radius once a container is compromised.
- ✓
Applying seccomp profiles to limit system call availability
Why this is correct
Seccomp restricts the system calls a container can make, reducing the attack surface.
Related concept
Authentication checks who the user is.
- ✓
Enforcing Pod Security Standards (PSS) such as 'restricted' policy
Why this is correct
PSS can prevent containers from running with elevated privileges, reducing impact of compromise.
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 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 CAS-004 questions on access control and AAA configuration.
- →
Security Architecture — study guide chapter
Learn the concepts, then practise the questions
- →
Security Architecture practice questions
Targeted practice on this topic area only
- →
All CAS-004 questions
510 questions across all exam domains
- →
CompTIA SecurityX CAS-004 study guide
Full concept coverage aligned to exam objectives
- →
CAS-004 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CAS-004 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Scripting, Containers and Automation practice questions
Practise CAS-004 questions linked to Scripting, Containers and Automation.
Application Environment, Configuration and Security practice questions
Practise CAS-004 questions linked to Application Environment, Configuration and Security.
Security Architecture practice questions
Practise CAS-004 questions linked to Security Architecture.
Security Engineering and Cryptography practice questions
Practise CAS-004 questions linked to Security Engineering and Cryptography.
Security Operations practice questions
Practise CAS-004 questions linked to Security Operations.
Governance, Risk, and Compliance practice questions
Practise CAS-004 questions linked to Governance, Risk, and Compliance.
Governance, Risk and Compliance practice questions
Practise CAS-004 questions linked to Governance, Risk and Compliance.
Security Engineering practice questions
Practise CAS-004 questions linked to Security Engineering.
CAS-004 fundamentals practice questions
Practise CAS-004 questions linked to CAS-004 fundamentals.
CAS-004 scenario practice questions
Practise CAS-004 questions linked to CAS-004 scenario.
CAS-004 troubleshooting practice questions
Practise CAS-004 questions linked to CAS-004 troubleshooting.
Practice this exam
Start a free CAS-004 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 CAS-004 question test?
Security Architecture — This question tests Security Architecture — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Implementing Kubernetes network policies to restrict pod-to-pod communication — Network policies restrict communication between pods, limiting lateral movement. Seccomp profiles restrict system calls, reducing attack surface. Pod Security Standards (PSS) enforce security contexts like not running as root. RBAC controls user access, not container-to-container. Image scanning identifies vulnerabilities but does not limit blast radius.
What should I do if I get this CAS-004 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 CAS-004 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 CAS-004 practice question is part of Courseiva's free CompTIA 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 CAS-004 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.