KCSA Kubernetes Threat Model Practice Question
A Kubernetes cluster experiences an attack where an untrusted pod attempts to access the Kubernetes API server and discover cluster secrets. The cluster uses RBAC. What is the mechanism that prevents this pod from reading secrets in other namespaces?
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
✓
Namespaced RoleBindings limiting permissions strictly to the pod's own namespace
Kubernetes RBAC RoleBindings are namespaced, meaning a Role or RoleBinding grants permissions only within the specific namespace where it is created, preventing cross-namespace access unless a ClusterRoleBinding is used.
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 the AlwaysAdmit authorization webhook mode
Why it's wrong here
AlwaysAdmit permits all requests and provides zero security isolation.
- ✗
Default ClusterRole bindings assigned automatically to all service accounts
Why it's wrong here
Default service accounts do not receive cluster-wide privileges automatically.
- ✗
NetworkPolicies blocking traffic directed at the Kubernetes API server port
Why it's wrong here
NetworkPolicies govern pod-to-pod traffic, while API server access is controlled via authentication and RBAC authorization.
- ✓
Namespaced RoleBindings limiting permissions strictly to the pod's own namespace
Why this is correct
Namespaced RoleBindings enforce isolation boundaries so that identities authorized in one namespace cannot access resources in another.
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 |
About these practice questions
Courseiva writes every KCSA question from scratch — 320 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed August 2026 · checked against the official CNCF / Linux Foundation exam blueprint
This KCSA practice question is part of Courseiva's free CNCF / Linux Foundation 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 KCSA exam.