How to Write CKA Scenario Items with Rationales (No Dump)
CKA drills collapse when they copy a leaked killer.sh stem or call Gateway API on a 1.31 cluster that does not have the CRD. Original tasks, a version lock, and a rationale are enough.
The matching generator is the CKA Scenario Item Writer with Rationales (No Dump) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Map items only to pasted headings
Write original CKA-style lab scenarios with rationales from pasted CNCF curriculum headings. No dumps, no kubectl invent beyond the version lock. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Curriculum headings I pasted: [Headings]
Cluster and kubectl version lock: [Version]
CNI and extra controllers I actually have: [Stack]
Namespaces and names I allow: [Names]
How many scenarios: [Count or 2]
Time box per scenario minutes: [Time]
Topics to skip: [Skip]
Facts I may use (CIDRs, storage class names): [Facts]
Words I must not use: [Banned]
Whether Helm is in scope: [Helm]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Lock kubectl and refuse newer APIs
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Banner: original practice, not the CNCF exam, not a dump. Quote Version.
- Item map: each scenario to a pasted heading. Reject Skip topics and anything not in Headings.
- Scenario stems: tasks a candidate could do with kubectl at Version. No recalled killer.sh wording. No invented API (for example Gateway API) unless Stack has it.
- Solution sketch: kubectl commands and YAML keys that exist at Version. Mark Helm steps only if Helm is yes.
- Rationale: why the correct approach matches the heading, and one plausible wrong turn.
- Cluster leftovers: what to delete so the next item is clean, using Names only.
- Refuse list: dumps, scored mocks that claim official weighting, CKS/CKAD crossover not in Headings.
- Compliance pass: quote Banned words, APIs newer than Version, invented StorageClass. Cut them.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Write a rationale and one wrong turn
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Original CKA-style practice. Never reproduce a live or leaked item.
- Lock kubectl and Kubernetes to Version. Do not use APIs from a newer minor.
- Not CKS, not CKAD, unless Headings are those programs.
- Do not invent Helm, Gateway API, or a cloud load balancer.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Skip Helm and Ingress when the brief skips them
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (cka scenario item writer, kubernetes cka practice, no exam dump) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.