No Docs Map — the CNPA Is Closed-Book

This page exists to correct one assumption before it costs you an exam attempt. If you have read the CNPE's docs map, or sat any performance-based Linux Foundation exam, you already carry a mental model: there's an allowlist somewhere, and if I learn its shape I'll be fine on the day. Drop that model entirely before you book the CNPA. There is no allowlist to learn, because there is nothing on it. The CNPA is fully closed-book — no kubernetes.io, no project docs, no notes, no man pages, nothing installed anywhere near you. This page states that plainly, contrasts it directly against the CNPE so the assumption doesn't quietly cross over, describes the general shape of the on-screen experience that follows from "closed-book, remote-proctored, multiple-choice," and explains why that single fact should reshape how you study from week one.

The fact, stated plainly and cited

☺ Like you're 10: No book. Not "a small book" — no book, no website, no notes, nothing.

Per the Linux Foundation's official Resources Allowed page: "Candidates are NOT PERMITTED to access tools, resources or external sites when taking the Linux Foundation Multiple Choice … Exams." The CNPA is a Linux Foundation Multiple Choice Exam. That sentence is the entire allowlist, and what it allows is nothing. Not kubernetes.io. Not a PDF you saved locally. Not a sticky note. Not a second monitor with your notes app open — that's also a conduct violation under the general proctoring rules, quite apart from the resources rule. There is no Quick Reference box, because there is no task pane to attach one to; a multiple-choice question either gives you everything you need in its stem, or it doesn't, and either way nothing external is coming to help.

The CNPA's own official page does not publish a question count, and no reliable, current, official figure exists to state here — a web search once surfaced a specific number for this exam, but that figure does not appear on the current training.linuxfoundation.org CNPA page, so this course does not repeat it and neither should you. What is published, and worth re-reading before you book, is the 120-minute duration and the 75% pass mark above — confirm both again on the official page in the week before your exam, because Linux Foundation exam terms are revised without much ceremony.

The CNPE contrast — so the assumption doesn't cross over

☺ Like you're 10: The CNPE test lets you bring one book. This test lets you bring nothing. Don't get the two tests mixed up in your head.

If you've read the CNPE docs map, you already know the CNPE permits a narrow but real set of resources: kubernetes.io/docs, kubernetes.io/blog, whatever task-specific pages the exam's own Quick Reference box links, and documentation installed locally on the exam machine. That is a genuine, usable allowlist — narrower than most candidates expect, but not empty. The CNPA's allowlist has one fewer item than that: all of them, simultaneously, are gone. Put the two side by side and the size of the gap should register properly, because "narrower" and "nonexistent" are different orders of problem.

Notice what this means concretely if you're moving from CNPE prep into CNPA prep, or vice versa. On the CNPE, "I don't remember the exact field name for a Kyverno rule" is recoverable — you read the Quick Reference box, or you fall back to kubectl explain on an installed CRD. On the CNPA, that same flicker of doubt about a term or a distinction is not recoverable at all. There is no box to open, no terminal to query, no cluster to poke at for a hint. Whatever is fuzzy in your head on exam day stays fuzzy for that question, permanently, for the two minutes you have to answer it.

What "closed-book, remote-proctored, multiple-choice" looks like on screen

☺ Like you're 10: One question at a time, a little flag button if you're unsure, and a list at the end showing everything you haven't finished — like a quiz app, not a computer terminal.

The following describes the general shape of a Linux Foundation multiple-choice exam interface, as candidates across the associate-tier catalogue (KCNA, KCSA, CGOA, and the CNPA among them) have reported it. Exam interfaces get revised by the platform provider without much notice, so treat this as "roughly what to expect," not a pixel-accurate walkthrough — confirm your own exam's exact UI on the day, during the tutorial screen the proctoring platform shows before your timer starts.

The practical consequence: your two real tools during the exam are flag-and-move and the final review pass. Neither tool helps you know something you don't know — they only help you spend the two hours efficiently across the questions you're capable of answering. That's a meaningfully smaller toolkit than the CNPE gives you, and it's precisely why the study strategy below has to be different in kind, not just in degree.

Why this changes study strategy fundamentally

☺ Like you're 10: For this test, "I could probably find it if I needed to" isn't good enough. You have to already know it, instantly, every time.

Three separate but related shifts follow directly from closed-book, and each one should show up in how you actually spend study hours, not just in how you feel about the exam.

Recognition must be instant and automatic

On an open-book exam, "I recognise that term, I could look up the exact definition" is a survivable state — you look it up, you confirm, you move on. On the CNPA, that same half-recognition is the failure state, because there is no next step available. A term you can place roughly but not define precisely, a distinction you can gesture at but not state crisply (self-heal versus prune, a golden path versus a mandate, RED versus USE, DORA's four metrics by name) has to become instant before exam day, not "good enough with a nudge." Drill with retrieval, not re-reading: close the page, say the definition out loud in one sentence, and only then check it. Know It Cold — the CNPA glossary you must have instant and the CNPA concept reference exist specifically to turn "roughly familiar" into "instant," and the flashcards are built for exactly this kind of drilling.

There is no partial-credit safety net of a live cluster to poke at

The CNPE's most forgiving property is that you're graded on resulting state, not on how you got there — and along the way, a live cluster is sitting in front of you the whole time, answering questions you didn't know to ask. Run kubectl get, and the cluster tells you whether your Rollout actually rolled out. Try kubectl explain, and the schema tells you the field name you'd half-forgotten. The CNPA offers none of that. There is no partial credit for "I understood the general shape of the idea" on a single-best-answer question — you pick one option, and it's either right or it isn't. There's no cluster to test a hunch against, no --dry-run to see what would happen. Whatever you bring into the question is the entirety of what you get to work with.

No lookup to lean on if a term is fuzzy

This is the same point as the first shift, stated as a study-planning consequence rather than an exam-day one: because there is no lookup at any point, every fuzzy term is a study debt you will pay for on exam day, at a moment you don't get to choose. The discipline this demands is different from CNPE prep, where "I'd need to check the exact syntax" is an acceptable gap to leave until the week before. For the CNPA, build a running list of every concept you can only gesture at — not name confidently, not define crisply — and treat that list as the actual syllabus. The triage page is built around exactly that idea: converting vague unease into a ranked list of what to drill next, because "closed-book" turns fuzzy recall from a minor inconvenience into the single biggest risk in your preparation.

Remote-proctoring logistics — the CNPA-specific slice

☺ Like you're 10: Someone watches you through your webcam, checks your ID, and looks around your room before you start — same as the harder test, just with no terminal and no browser to argue about.

The identity, room-scan and application-window rules are shared across the whole Linux Foundation catalogue and are covered in full on the exam-day and proctoring page — read that page for the complete treatment of ID requirements, the name-match rule, the room scan, check-in timing, and what happens if the proctor interrupts you. What's worth restating here, scoped specifically to the CNPA, is how those shared rules land differently when there's no allowlist to argue about at the edges.

• Government-issued photo ID with your name and signature, matching your registration exactly (including script — Kanji stays Kanji, Chinese characters stay Chinese characters, no romanising to "help"), checked live by the proctor before anything else happens.
• A room scan — a slow pan of your desk, walls and the space around you, done before the exam is released, to confirm there's nothing external in reach. For the CNPE this scan is partly about physical notes standing in for the documentation you're not allowed; for the CNPA it's the same physical check, but there is no partial exception to look for — the desk simply needs to be empty, because absolutely nothing besides the machine in front of you is permitted at any point.
• No other applications or browser windows. This is where the CNPA's closed-book rule and the general conduct rule reinforce each other rather than being two separate concerns. On the CNPE, "no other windows" still leaves you a browser tab pointed at kubernetes.io, inside the one window you're allowed. On the CNPA, "no other windows" combined with "no permitted resources of any kind" means the one window you get shows you nothing but the question interface itself — there is no tab to have open even if you were allowed a second window.
• No scratch paper, no local notes, no second monitor — identical to the CNPE's desk rules, but with no notepad-in-the-interface consolation prize on the other side of it. Whatever working you need to do, you do in your head.

The thesis of this page is narrow and worth carrying forward into everything else you read about the CNPA: there is no reference to lean on, so there is no substitute for having the material genuinely, instantly, in your head. Take that seriously in the study plan, drill it against the glossary you must have cold and the concept reference, use triage to find your weak spots honestly, and rehearse the shared logistics on the exam-day page so nothing procedural costs you an attempt you were otherwise ready for.