Certifications · CNPA · Mock Exam · Set 1

CNPA Mock Exam · Set 1

Sixty multiple-choice questions, weighted question-for-question to the six domains of the official CNPA curriculum — twenty-two on Core Fundamentals, twelve on observability, security and conformance, ten on continuous delivery, seven on platform APIs, five on IDPs and developer experience, four on measuring. This is the first of four CNPA papers and the one to sit first: it leans on recall and definitions, so it maps your vocabulary before Set 2, Set 3 and Set 4 start asking you to apply it. The four papers are four sittings, not four disjoint question pools: roughly half of each is fresh, and the rest deliberately comes back to the same core propositions in different words. That overlap is concentrated where the blueprint is heaviest — Core Fundamentals alone is 36%, twenty-two questions on every paper, and that topic does not hold eighty-eight distinct propositions. Meeting an idea again days later is spaced retrieval practice, and it tells you something: instant recall means it has consolidated, hesitation means it never had. The CNPA is a knowledge-based exam, so this is a question paper, not a lab: there is nothing to install and no cluster to break. Answer cold, one pass, no notes. Every question gives you the answer and a short explanation of why the moment you commit, and the domain chips let you re-sit a single domain once you know where you are weak.

How to sit this paper

☺ Like you’re 10: Set a timer, close every other tab, and go straight through without stopping to look things up.

The value of a mock is destroyed by looking things up mid-paper — you end up measuring your search skills instead of your recall. So treat this like the real sitting: one uninterrupted block, no documentation, no other tabs, and a decision on every question even when you are guessing. Nothing published indicates that Linux Foundation multiple-choice exams deduct marks for a wrong answer — treat that as an assumption to confirm on the official page rather than a fact you got here — but the advice holds either way: never leave a question blank; eliminate the two obviously wrong options and pick the better of what remains. The wider sitting technique lives in the exam guide and the exam-prep checklist.

The protocol

1. Set a clock for 120 minutes — that is the duration the Linux Foundation allows CNPA candidates, and across sixty questions it works out at a full two minutes each. Multiple-choice exams are otherwise 90 minutes; the CNPA is the published exception, so do not drill at ninety seconds a question when the real sitting gives you two minutes. If you are still running out of time, that is itself a finding.
2. Leave the chips on “All” for the first sitting. Domain-filtering is a revision tool, not an exam tool.
3. Answer, then read the explanation. If it merely confirms what you thought, move on. If it surprises you, write the topic down — that list is your revision plan.
4. Do not re-take immediately. Go and read the two weakest domain pages first; a second pass an hour later measures short-term memory, nothing more.
5. Then re-sit by domain using the chips, and use Shuffle / reset — both the question order and the answer options are reshuffled each time, so you cannot pass by remembering “it was the third one.”

What this paper deliberately is not

It is not a leaked or reconstructed exam, and the wording is ours, not the CNCF’s. Three more honest caveats. First, the real exam’s question count is set by the Linux Foundation and may not match the sixty questions here; the duration we do know — 120 minutes — and this paper is deliberately sized to be sat inside it. See the warning below. Second, a mock can only test what it can phrase as a question; the CNPA also rewards being able to explain a concept in a sentence, which is why Master Panda’s blank-sheet drill belongs in your plan alongside this paper. Third — and this is the one people get wrong — a multiple-choice paper is the right shape of practice only because the CNPA is a knowledge-based exam. It sits in the associate, knowledge-based tier next to KCNA, KCSA and CGOA: you choose answers, you never touch a cluster. The performance-based exams — CKA, CKAD, CKS and the CNPE — drop you into a live terminal and grade the resulting cluster state, and no quantity of multiple choice prepares you for that. For those, the practice that counts is the lab track, the practice-task bank and a timed sitting of Mock Exam Set 1. See the certifications overview for the full tier map.

How the sixty questions are weighted

☺ Like you’re 10: The questions are shared out the same way the real test shares out its marks — the biggest topic gets the most questions.

The six published weights — 36, 20, 16, 12, 8 and 8 — sum to exactly 100%, and each domain’s share of this paper tracks its weight as closely as sixty whole questions allow. Only the rounding differs, and it is worth doing the arithmetic in full because the split is not obvious. Sixty questions against the six weights gives 21.6, 12.0, 9.6, 7.2, 4.8 and 4.8. Observability lands exactly on 12 and needs no rounding at all; Core Fundamentals (21.6) and Continuous Delivery (9.6) round up to 22 and 10; Platform APIs (7.2) rounds down to 7. That leaves the awkward case: IDPs & DevEx and Measuring are both 8%, so both come out at 4.8, and a tie has to be broken somewhere. Round both up and the paper is 61 questions; round both down and it is 59. So one goes each way — IDPs & DevEx takes five, Measuring takes four — and 22 + 12 + 10 + 7 + 5 + 4 is exactly 60. The shape of your result therefore maps onto the shape of the real exam. Core Fundamentals alone is more than a third of it; miss badly there and no amount of tooling detail elsewhere rescues the score.

The paper — sixty questions

☺ Like you’re 10: Pick an answer. It turns green or red straight away and tells you why.

Click an option to lock it in — the correct answer is marked, your mistake is marked, and the explanation appears underneath. The counter and bar at the top track how far through you are and how many you have right. The chips filter by domain; Shuffle / reset reshuffles everything and starts a fresh attempt.

Marking yourself, and what to do next

☺ Like you’re 10: Your score is not the point. The list of things you got wrong is the point.

The counter gives you a percentage; treat it as a thermometer, not a verdict. The number to beat is 75%: the Linux Foundation’s Multiple Choice Exam FAQ states that a score of 75% or above must be earned to pass a multiple-choice exam, and the CNPA is one. Re-check it before you book — these terms do change — but do not treat it as folklore. What you should not do is read 75% here as a pass there: this paper is not calibrated to the real exam’s difficulty, and the wording is ours. What travels reliably is the pattern:

Whatever you scored, do one more thing before you close the tab: take every question you got wrong and write, in your own words, why the option you chose was wrong. Not why the right one was right — why yours was wrong. That is the sentence that stops you making the same mistake in the exam.

Where each domain is taught

☺ Like you’re 10: Every question here comes from one of six pages. Go back to the page, not to the internet.

Nothing in this paper is examined that is not taught in the sub-course. The six domain pages are the direct answer key at exam depth, and the CNPA hub maps each of them to the deeper CNPE lessons on the same ground if you want more than the associate exam asks for.

Beyond the sub-course, the shared revision kit still applies: the self-check quiz for mixed CNPE-flavoured recall, the flashcards for the vocabulary, the glossary for anything a question assumed you knew, know it cold for the handful of things that have to be automatic, the exam-prep checklist for the week before the sitting, and the certifications overview when you want to know what to take next.