// Generate CKA exam-realistic practical scenarios that match the format, difficulty, and style of real CKA performance-based tasks. Each scenario presents a task the candidate must complete using kubectl commands against a Kubernetes cluster. Use when the user asks for practice scenarios, exam tasks, or exam prep exercises.
| name | cka-scenario-creator |
| description | Generate CKA exam-realistic practical scenarios that match the format, difficulty, and style of real CKA performance-based tasks. Each scenario presents a task the candidate must complete using kubectl commands against a Kubernetes cluster. Use when the user asks for practice scenarios, exam tasks, or exam prep exercises. |
Description: Generate CKA exam-realistic practical scenarios that match the format, difficulty, and style of real CKA performance-based tasks. The CKA exam is 100% performance-based -- there are no multiple-choice questions. Candidates execute real commands against live clusters.
Required sources:
references/cka-objectives.md for the full CKA v1.35 curriculum objectivesreferences/style-guide.md for writing style and Kubernetes conventionsAllowed reference domains (matching real exam):
Follow all rules in references/style-guide.md. Key rules for scenarios:
Code style for kubectl commands, YAML keys, resource names, file paths, namespaces, and image names.Exam integrity:
Technical accuracy:
references/style-guide.md for the API version table).Content quality:
Use fictional company names from references/fictional-companies.md for scenario context. You MUST randomize the company selection -- do not default to Globomantics for every scenario. Draw from the full list of 25+ companies.
Every scenario must include a context-switch command. Use cluster names from this list:
k8s-prod -- production cluster (most common)k8s-staging -- staging environmentk8s-dev -- development clusterek8s -- etcd-focused tasks (ETCD backup/restore, HA control plane)mk8s -- multi-node cluster tasks (kubeadm, node management)wk8s -- worker-node focused tasks (scheduling, affinity, taints)Match the cluster to the scenario type. For example, etcd tasks use ek8s, scheduling tasks use wk8s.
| Difficulty | Estimated time | Example tasks |
|---|---|---|
| Easy | 2-3 minutes | Create a Pod, expose a Service, create a ConfigMap, create a Secret |
| Medium | 4-5 minutes | Configure RBAC, create a NetworkPolicy, set up HPA, configure a PersistentVolumeClaim |
| Hard | 6-8 minutes | ETCD backup and restore, kubeadm cluster upgrade, Gateway API routing, troubleshoot a multi-component failure, configure a CRD and operator |
references/cka-objectives.md.references/fictional-companies.md and draft a workplace scenario.When presenting a scenario to the user:
Phase 1 -- Scenario only:
Show metadata, context-switch command, and task description. Do NOT include the solution, explanation, verification, or references. End the message and wait for the user to request the solution.
Phase 2 -- Solution:
After the user requests the solution (by typing "solution," "show solution," "answer," "reveal," or similar), show:
If multiple scenarios were requested, repeat this Phase 1 / Phase 2 cycle for each scenario sequentially.
When multiple scenarios are requested:
Phase 1 message (scenario only):
### CKA Practice Scenario [N of M]
**Domain:** <domain name> (<weight>%)
**Objective:** <specific objective from cka-objectives.md>
**Difficulty:** <easy | medium | hard>
**Estimated time:** <2-8 minutes>
**Cluster:** <cluster name>
---
Set the correct cluster context:
`kubectl config use-context <cluster-name>`
**Task:**
<Company context sentence.> <Specific task description with measurable completion criteria. Include namespace, resource names, image names, port numbers, and any other specifics the candidate needs.>
(Stop here. Wait for the user to request the solution.)
Phase 2 message (solution, after user requests it):
### Solution
#### Step-by-step commands
1. Set the cluster context.
```bash
kubectl config use-context <cluster-name>
<command>
<...continue for all steps>
<Commands to verify the solution is correct, with expected output described>
---
## Prompt template
```text
Create {{count}} CKA exam-realistic practice scenarios.
Inputs:
- domain: {{domain}} (or select from CKA curriculum)
- objective: {{objective}} (or derive from curriculum)
- difficulty: {{difficulty}} (easy | medium | hard)
Requirements:
1. Ground every scenario in official Kubernetes documentation first.
2. Follow guardrails and output format exactly.
3. Randomize the exam cluster assignment appropriately.
4. Randomize the fictional company name from references/fictional-companies.md.
5. Use two-phase delivery: scenario first, solution only after requested.
Deliver {{count}} scenarios.
Create guided hands-on CKA practice labs (15-30 minutes) that run on kind clusters. Every lab includes prerequisites, step-by-step instructions with explanations, validation gates, troubleshooting tips, and cleanup. Use when the user asks for a hands-on lab, guided exercise, or learning walkthrough.
Generates a personalized CKA study plan based on the user's self-assessed confidence across the five exam domains, prioritizing weak areas with estimated hours and Kubernetes documentation links. Use when the user asks for a study plan, is unsure what to study, or wants exam prep guidance.