KCSA Kubernetes Threat Model Practice Question
In a zero-trust Kubernetes architecture, an attacker attempts to exploit the Kubernetes API server via a Server-Side Request Forgery (SSRF) flaw in a poorly written custom controller. Which defense-in-depth mechanism specifically protects against unauthorized API requests originating from inside the cluster network?
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
✓
Mandatory client certificate authentication and rigorous RBAC authorization on API endpoints
Mutual TLS (mTLS) authentication combined with RBAC ensures that callers must present a valid, cryptographically signed client certificate and have explicit authorization rules to talk to the API server.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configuring Horizontal Pod Autoscalers to limit request rates
Why it's wrong here
HPA scales workload replicas based on metrics, offering no protection against unauthorized API requests.
- ✗
Enabling Pod Security Standards in baseline mode across all namespaces
Why it's wrong here
Pod Security Standards restrict pod runtime privileges, not network-level API interactions.
- ✓
Mandatory client certificate authentication and rigorous RBAC authorization on API endpoints
Why this is correct
The API server requires valid credentials (like a service account token or client cert) and RBAC verification for all requests, preventing anonymous or under-privileged internal access.
- ✗
Disabling the Kubelet read-only port on all worker nodes
Why it's wrong here
While disabling the legacy read-only port (10255) is an important hardening step, it secures the Kubelet rather than protecting the API server from SSRF.
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
This KCSA question is part of Courseiva's 320-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 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.