SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
KCSA practice

Free KCSA practice questions

Drill exam-realistic Kubernetes and Cloud Native Security Associate (KCSA) questions by domain, with an explanation on every option — not just the right one. 5 fully worked examples are further down this page, answers included.

Question bank
387
across 6 domains
Free, no account
5/day
a free account allows 10 a day
Real exam
60 Qs
90 min · pass 75%
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across all domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

5 sample KCSA questions, fully explained

Real questions from the KCSA bank, with the answer key and the reasoning behind every option. Read them, then go back up the page and try the rest.

Question 1Overview of Cloud Native Security

A team sets network ACLs outside the cluster, in front of the Kubernetes API endpoint, so that only the administrators' IP ranges can reach it. In the 4Cs model, which layer does this control belong to?

Choose one.

  • a
    The Cloud layer Correct

    The Kubernetes 4Cs guidance lists network access to the API server under infrastructure (Cloud layer) security: provider network ACLs limit who can even reach the endpoint.

  • b
    The Cluster layer

    Cluster-layer controls are configured inside Kubernetes (RBAC, admission, NetworkPolicy). A network ACL set outside the cluster, in front of the endpoint, is configured in the infrastructure.

  • c
    The Container layer

    The Container layer covers images and the runtime settings of containers, not network reachability of the control plane.

  • d
    The Code layer

    The Code layer covers the application's own code and its endpoints, not the cluster's API endpoint.

The concept

The 4Cs are Cloud (or corporate data centre / co-location), Cluster, Container and Code; the Cloud layer is the infrastructure the cluster runs on.

Why that’s the answer

The control is a network rule set in the infrastructure the cluster runs on, outside Kubernetes, so it sits in the outermost layer, Cloud. The Kubernetes guidance on infrastructure security names 'network access to the API server' as a Cloud-layer item: the control plane should not be publicly reachable and should be limited by network ACLs to the addresses that administer it. It is tempting to call it Cluster because it protects the API server, but Cluster-layer controls are the ones configured through Kubernetes itself.

How to reason it out
  1. Ask where the control is configured: in the provider's infrastructure or inside Kubernetes.
  2. A network ACL set outside the cluster is infrastructure, so it is a Cloud-layer control.
  3. Reserve Cluster for Kubernetes-native settings such as RBAC and NetworkPolicy.

Exam tip: Configured in the infrastructure outside Kubernetes = Cloud layer, even when it protects a Kubernetes component.

KCSA: The 4Cs of Cloud Native Security, Infrastructure Security and Security Controls — the lesson that teaches this.

Question 2Kubernetes Cluster Component Security

A developer runs kubectl apply to create a Deployment. In which order does the kube-apiserver process the request before the object is stored in etcd?

Choose one.

  • a
    Authorization, then authentication, then admission control

    Authorization needs an identity to evaluate, so it cannot run before authentication has produced one.

  • b
    Authentication, then authorization, then admission control Correct

    The API server first establishes who the caller is, then checks whether that identity may perform the action, then runs admission controllers before persisting the object.

  • c
    Authentication, then admission control, then authorization

    Admission controllers run only on requests that are already authorized; authorization comes first.

  • d
    Admission control, then authentication, then authorization

    Admission is the last gate before storage, not the first; an unauthenticated request never reaches it.

The concept

Every API request passes authentication, authorization and admission control, in that order, before the object is persisted to etcd.

Why that’s the answer

The API server cannot decide permissions without knowing the caller, so authentication comes first and authorization second. Admission controllers (mutating, then validating) only see requests that already passed both, which is why they can inspect and change the object itself. The near-twins simply swap two of the stages.

How to reason it out
  1. Ask what each stage needs as input: authorization needs an identity.
  2. Recall that admission works on the object of an already-permitted request.
  3. Pick the order authentication → authorization → admission → etcd.

Exam tip: Who are you, are you allowed, is this object acceptable - then it is written to etcd.

KCSA Control Plane Security: API Server, Controller Manager, Scheduler and etcd — the lesson that teaches this.

Question 3Kubernetes Security Fundamentals

Which description matches the Baseline profile of the Kubernetes Pod Security Standards?

Choose one.

  • a
    An unrestricted policy that permits known privilege escalations for trusted workloads

    That is the Privileged profile, which is defined by an absence of restrictions and is meant for system and infrastructure workloads run by trusted users.

  • b
    A heavily restricted policy that applies current Pod hardening practice at some compatibility cost

    That is the Restricted profile, aimed at security-critical applications and lower-trust users; it adds controls such as running as non-root on top of Baseline.

  • c
    A policy that rewrites incoming Pod specs to add safe default values before admitting them

    The standards only describe which values are acceptable; defaulting Pod fields was a feature of the removed PodSecurityPolicy, and Pod Security Admission does not mutate Pods.

  • d
    A minimally restrictive policy that blocks known privilege escalations but admits default Pods Correct

    Baseline is aimed at ease of adoption: it blocks known privilege escalations such as privileged containers or host namespaces, while a minimally specified Pod still passes.

The concept

The Pod Security Standards define three cumulative profiles: Privileged, Baseline and Restricted.

Why that’s the answer

Baseline sits in the middle: it prevents known privilege escalations yet still admits the default, minimally specified Pod, which makes it easy to adopt for common workloads. Privileged is the open end of the range and Restricted the hardened end. None of the profiles changes a Pod; they only define which settings are allowed.

How to reason it out
  1. Recall the three profiles in order from most open to most restrictive.
  2. Match 'blocks known escalations but admits default Pods' to the middle profile.
  3. Discard the mutating option: the standards only validate.

Exam tip: Privileged = no limits, Baseline = no known escalations, Restricted = hardening best practice.

KCSA Pod Security Standards and Pod Security Admission — the lesson that teaches this.

Question 4Kubernetes Threat Model

In threat modeling a Kubernetes cluster, what is a trust boundary?

Choose one.

  • a
    A namespace that separates one team's workloads from another team's workloads

    A namespace is a scope for names and policies; by itself it does not isolate traffic or nodes, so it is not the definition of a trust boundary.

  • b
    A network segment that the cluster's control plane components alone can reach

    A control-plane-only network is one way to protect a boundary, not what a trust boundary is.

  • c
    A set of RBAC rules that limits which verbs a user can run against a resource type

    RBAC is a control applied at a boundary (the API server), not the boundary itself.

  • d
    A point where requests or data pass between less and more privileged components Correct

    A trust boundary is where privilege changes along a flow, such as an external client reaching the API server or a container calling into its node; these are the places controls must check what crosses.

The concept

A trust boundary marks where trust changes along a data flow.

Why that’s the answer

Threat models draw trust boundaries wherever data or execution moves between components that trust each other differently: the internet and the API server, the control plane and the nodes, a container and the host kernel, one workload and another. Namespaces, private networks and RBAC are controls that defend those boundaries; they are not the definition.

How to reason it out
  1. Ask what the term describes, not which control enforces it.
  2. Recall that boundaries sit where privilege levels differ along a data flow.
  3. Discard options that name a specific control or scope.

Exam tip: Trust boundary = where trust changes; controls sit on it.

KCSA Kubernetes Trust Boundaries, Persistence and Denial of Service — the lesson that teaches this.

Question 5Platform Security

A vendor ships each container image with a software bill of materials (SBOM). What information does the SBOM give the customer?

Choose one.

  • a
    A record of which build system, source commit and steps produced the image

    That describes build provenance (for example a SLSA provenance attestation), not a bill of materials.

  • b
    A list of the known vulnerabilities that were found in the image at release

    A vulnerability report is the output of a scanner at one point in time; an SBOM lists components, which can later be matched against new CVEs.

  • c
    An inventory of the packages, libraries and versions inside the image Correct

    An SBOM is a machine-readable list of the components (and their versions and suppliers) that make up the software, so users can see what they are running.

  • d
    A cryptographic signature that proves who published the image and its digest

    Proving publisher and integrity is the job of an image signature, such as one made with Sigstore cosign.

The concept

An SBOM is an ingredient list for software.

Why that’s the answer

A software bill of materials lists the components of an artifact: operating-system packages, language libraries, their versions and often their suppliers and licences. It does not say how the artifact was built (provenance), whether it is vulnerable right now (a scan result) or who published it (a signature), although an SBOM can itself be signed and attached as an attestation.

How to reason it out
  1. Ask what kind of record an SBOM is: an inventory.
  2. Separate it from provenance (how it was built) and signatures (who published it).
  3. Note that vulnerability status changes over time while the inventory does not.

Exam tip: SBOM = what is inside; provenance = how it was built; signature = who published it.

KCSA Supply Chain Security, Image Registries and Admission Control — the lesson that teaches this.

The KCSA question bank, by domain

The bank is built to the exam's own weighting, so the practice you get reflects the marks that are actually on offer — not whichever domain was easiest to write questions for.

Published KCSA practice questions per exam domain
DomainExam weightTopicsQuestions
Overview of Cloud Native Security14%250
Kubernetes Cluster Component Security22%387
Kubernetes Security Fundamentals22%387
Kubernetes Threat Model16%262
Platform Security16%262
Compliance and Security Frameworks10%139
Total100%13387

Practise KCSA one domain at a time

How KCSA questions are worded

Most KCSA questions are not asking whether you can recall a definition. They describe a situation and ask which option satisfies it — so the skill being tested is reading the requirement precisely and eliminating options that fail it.

Single-response vs multiple-response

A single-response question has exactly one right answer. A multiple-response question tells you how many to pick ("Choose TWO") and there is no partial credit — getting one of the two right scores nothing. Read that instruction before you read the options.

Read the last line first

The final sentence is the actual question; everything before it is scenario. Read it first, then read the scenario knowing what you are looking for. It stops you from building an answer in your head that the question never asked for.

Hunt for the qualifier

Most scenarios turn on one word — MOST cost-effective, LEAST operational overhead, with the LEAST latency, without changing application code. Two options are frequently both technically correct, and the qualifier is the only thing separating them.

Eliminate, then choose

Distractors are almost always real CNCF services doing a real job — just not this job. Rule out the ones that break a stated constraint before you compare what's left. On a question you truly don't know, eliminating two options turns a guess into a coin flip.

Practise KCSA from your browser

The SaveMyCert Chrome extension opens a daily drill of 5 KCSA questions in the side panel, with the full explanation behind every answer. No account needed.

Get the Chrome extension (opens in a new tab)

Beyond KCSA practice

KCSA practice questions: your questions

Yes. You can answer 5 questions a day with no account at all, and a free account raises that to 10 a day across the full 387-question KCSA bank, with an explanation on every option. Pro removes the daily cap entirely.

Source

Exam structure, domain weights and scoring on this page come from the official KCSA exam guide.