Mock exams

kubefit test cka        # 8 tasks
kubefit test ckad 5     # 5 tasks

A mock exam runs several tasks back to back on one clock. Tasks are sampled by the same priority the scheduler uses, so a mock leans toward your weak, heavy-weight domains rather than a random spread. The cluster is repaired between tasks.

Flow

1. The first task prints and the clock starts.
2. Work in the drill shell as usual. kubefit grade checks the current task; exit moves to the next one.
3. After the last task, kubefit prints the summary: each task's outcome, its time against target, and the total.

Each task is recorded as its own rep with the mode mock, so it counts in reports like any other attempt.

--tmux and --enter work the same as for drills. In --enter mode, f finishes the current task as is and q abandons the rest of the exam.

Advice

Set a real time budget before you start: the number of tasks times a realistic share of the exam. Do not grade after every command. In the exam you get no grader, so use kubefit grade the way you would use your own verification commands, then move on.