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

Free KCSA mock exams

Full-length Kubernetes and Cloud Native Security Associate (KCSA) rehearsals: 60 questions in 90 minutes, drawn to the official domain weights and scored on the same scale as the real exam. Pass mark 750 / 1000.

Questions
60
~1.5 min each
Time limit
90 min
server-timed
Pass mark
750
on a 100–1000 scale
Papers
3
retake any of them
Create a free account to try a 10-question mock
Attempts are timed, saved and scored — you need somewhere to keep them.

Try a free 10-question mock

Free

10 questions across every domain in 15 minutes, timed and scored on the 100–1000 scale like the real exam, with every answer explained afterwards. One per exam, free with an account.

KCSA Mock Exam 1
60 questions · 90 min
New
Not attempted yet
KCSA Mock Exam 2
60 questions · 90 min
New
Not attempted yet
KCSA Mock Exam 3
60 questions · 90 min
New
Not attempted yet

More ways to rehearse

Every attempt draws questions you haven't met yet first · Pro.

Hard mode

A full-length paper drawn to the same domain weights, from the questions we rate hardest — the ones that combine two facts or weigh workable options against each other.

60 questions · 90 min
Timed domain drills

One exam domain at the real exam's pace — for the domain your last mock went worst in.

Overview of Cloud Native Security25 questions · 38 min
Kubernetes Cluster Component Security25 questions · 38 min
Kubernetes Security Fundamentals25 questions · 38 min
Kubernetes Threat Model25 questions · 38 min
Platform Security25 questions · 38 min
Compliance and Security Frameworks25 questions · 38 min

What's in a KCSA mock paper

Each paper draws its questions per domain in the same proportions CNCF publishes for the real KCSA — so a mock that goes badly in one domain is telling you something a randomly-drawn quiz couldn't.

Questions drawn per exam domain in a KCSA mock paper
DomainOfficial weightQuestions drawnShare of paper
Overview of Cloud Native Security14%813%
Kubernetes Cluster Component Security22%1322%
Kubernetes Security Fundamentals22%1322%
Kubernetes Threat Model16%1017%
Platform Security16%1017%
Compliance and Security Frameworks10%610%
Total100%60100%

What a KCSA paper is shaped like

Which way this particular paper applies pressure.

The clock

At roughly 1.5 minutes a question, the pacing is comfortable but not generous. You can afford to think on a hard question, and you cannot afford to do it twice. Most candidates finish with time for a second pass if they keep the first pass moving.

The weighting

The weighting is unusually flat — 6 domains with no single one dominating, the largest being Kubernetes Cluster Component Security at 22%. Nothing can be safely skipped, and there is no high-weight domain to carry a gap. Breadth beats depth on this paper.

The standard

The pass mark of 750 on the 100–1000 scale is at the stricter end. Treat a mock result that lands just over the line as a fail in disguise — the margin you want before booking is wider here than on a 100–1000 exam that passes lower.

Pacing a KCSA paper

Where you need to be on the clock, quarter by quarter.

Checkpoints for a full-length KCSA paper
CheckpointElapsedBe at questionQuestions left
First quarter23 min1545
Halfway45 min3030
Three quarters68 min4515
Time called90 min600

What trips people up on a KCSA mock

KCSA is a multiple-choice exam about security decisions, not a lab like CKS. Most questions describe a cluster, a workload or an incident and ask which control fixes it, and the wrong options are usually real Kubernetes controls applied at the wrong layer: RBAC offered for a network problem, a NetworkPolicy offered for an API permission, image scanning offered for a runtime threat. Before you look at the options, name the layer the problem lives in.

The two cluster domains, component security and security fundamentals, carry the largest share of the paper between them. A weak result in either one is hard to make up elsewhere, so check them first in the per-domain breakdown. Within them, the API server, the kubelet, Pod Security Admission and RBAC come up again and again.

Outdated material is the most common cause of wrong answers. PodSecurityPolicy is gone, a ServiceAccount no longer gets a long-lived token Secret automatically, and a Secret is only encoded, not encrypted, unless encryption at rest is configured. If you learned Kubernetes security from older guides, misses that cluster on these points mean the notes need updating, not more practice.

The threat-model questions ask how an attacker moves: from a compromised container to the node, from one Pod to another across the network, or from a stolen token to the API. Answer by asking which trust boundary the attacker has just crossed and which control would have stopped them there. Candidates who know the controls but cannot place them on that path lose marks here even when their fundamentals scores are high.

The pass mark sits at the strict end of the scale, so count a borderline mock as a fail. The compliance and platform domains are smaller, but questions on frameworks, supply-chain controls and admission policy test vocabulary that rarely comes up in day-to-day cluster work. They are the quickest marks to add before the real exam.

Before you sit a KCSA mock

KCSA mock exams: your questions

60 questions in 90 minutes. Every mock exam here matches that format exactly, and is weighted across the domains the same way the real KCSA is.

Source

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