Troubleshooting·Kubernetes and Cloud Native Security Associate
Commonly Confused KCSA Concepts
Multiple-choice security questions are built on distinctions: two things that sound the same and behave differently. This guide takes the six that the KCSA pool leans on hardest and settles each one against a live cluster, so the answer is a measurement rather than a memory.
Working at Exam Speed Guide 41 of 42 Intermediate
- Kubernetesapiserver v1.36.4, kubelet v1.36.3
- Runtimecontainerd 2.2.6
- CNICilium 1.18.1 - tunnel/VXLAN, with Hubble relay and UI
- Host OSUbuntu 26.04 LTS, kernel 7.0.0-29
- Built withkubeadm v1.36.3 - podSubnet 10.244.0.0/16, serviceSubnet 10.96.0.0/12
- TimeAbout 16 min
- Reviewed25 August 2026
Written against the versions above. Every pair here is default behaviour on a stock kubeadm cluster. Nothing depends on this cluster's CNI or on anything installed.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA5001 | 192.168.0.41 | Ubuntu 26.04 LTS | Control Plane Node (tainted NoSchedule) | 2 Core | 4 GB | 50 GB |
| CKA5001-NODE01 | 192.168.0.42 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA5001-NODE02 | 192.168.0.43 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA5001-NODE03 | 192.168.0.44 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
-
view against edit, on the resource that matters
-
The other half of the same difference
-
A resourceName that works on one verb and not the other
-
Request equals limit, and still not Guaranteed
-
baseline against restricted, on the identical Pod
-
The status code that is not the one you expect