This check verifies that you can find, without help, the object or command that answers a situation from the Fundamentals module. The quiz mixes questions on orchestration, the basic objects, the installation of kubectl, the local cluster, the kubectl context, the first deployment and reading the state of a Pod. You then read your score theme by theme, to know which lesson to go back to. The end-of-module challenge asks you to redo this path on a real cluster, without step-by-step instructions.
What you will learn
- Find without help the object or command that answers a situation from the module
- Read your score by theme and designate the lesson to go back to
- Ship an application that is deployed and exposed, then read and repair a failure, in a challenge graded on the final state of the cluster
Prerequisites
Take this check after the lessons of the module: why orchestrate, the key concepts, the installation of kubectl, the first cluster, the kubectl contexts, the first deployment and reading the cluster state. Without them, the score would not measure what you learned.
Start the quiz
The questions are drawn from each of the lessons of the module. Answer in one go, without going back to the guides: a score obtained by rereading says nothing about what is really acquired. At the end, each answer points to the section of the lesson that teaches it.
Knowledge check
Check what you have learned with this interactive quiz
How it works
- The timer starts when you click Start
- Multiple choice, true/false and short answer questions
- You can move between questions
- Detailed results are shown at the end
Starts the quiz and the timer
Review
(0/0)Score by domain
A domain groups several guides and gets several questions, so its score is more reliable than a per-topic score, which often rests on a single question.
Summary
Strengths
No topic passed at 80% on at least two questions yet.
Weak areas
No topic below the pass mark.
Recommended next
Hints before you try again?
Continue the course: Kubernetes architecture: understand the cluster in 15 minutes
A new full quiz with random questions
Work again only on the questions you missed
Read your result
The threshold is set at 80%. Below it, go back to the cluster rather than to the text alone: redoing the lesson's gesture fixes the notion better than rereading it.
Spot the questions you missed, group them by theme with the table, then go back over the corresponding lesson before restarting the quiz.
| If you missed questions about… | Go back to the lesson |
|---|---|
| what an orchestrator brings, the desired-state loop | Why orchestrate containers |
| Node, Pod, Deployment, Service, Namespace | Key concepts |
| kubectl version, binary checksum, autocompletion | Install kubectl |
| creating, stopping and deleting a kind cluster | First cluster with kind |
| kubeconfig, active context, default namespace | Kubeconfig and contexts |
create deployment, expose, scale, labels and endpoints | First deployment |
get, describe, logs, top, error statuses | Read the cluster state |
Put it into practice
The quiz checks that you recognize the right answer. The challenge checks that you know how to do it: it gives an objective, not the commands. You ship a web application, the storefront, then you bring back a Deployment whose Pods do not start, the stock service. It is graded on the final state of the cluster, not on the commands you typed, with a threshold of 70 and two blocking requirements: the storefront must answer over HTTP from inside the cluster, and ~/.kube/boutique.yaml must have 600 permissions. A blocking requirement that is not met fails the challenge, whatever the score.
The seven requirements all weigh the same. No hint is offered. Six requirements met give about 86 points, five give about 71, just above the threshold, and four give about 57, below it. With five requirements met, the margin is therefore very thin, and the two blocking requirements must be among them.
While you work, dsoxlab check shows what still fails. When you think you are done, dsoxlab submit returns the verdict: the score, the threshold and the blocking requirements.
Seven states are checked, and each one refers to a lesson of the module:
- the active context is
kind-boutiqueand its default namespace isvitrine(lesson Kubeconfig and contexts); - the
vitrineDeployment has its three replicas available, on the reference image (lesson First deployment); - the
vitrineService has three ready endpoints (same lesson); - the storefront answers over HTTP from inside the cluster, a blocking requirement (same lesson);
~/boutique/cause-stock.txtnames the reason for the failure and the faulty image, and it is written before the repair (lesson Read the cluster state);- the
stockDeployment is repaired in~/boutique/stock.yamland applied withkubectl apply: akubectl set imagedoes not count (First deployment lesson, section on the declarative method); - the
~/.kube/boutique.yamlkubeconfig is readable only by its owner, with600permissions, a blocking requirement (Kubeconfig and contexts lesson).
A state that fails tells you what is missing, without saying how to fix it. The lesson to go back to is the one that teaches that state: reread it, redo the gesture on your cluster, then run dsoxlab check again.
Key takeaways
- The review quiz draws questions from each lesson of the module, and its score by theme designates the lesson to go back to.
- Below the 80% threshold, redo the lesson's gesture on your cluster before restarting the quiz.
- The module challenge is graded on the final state of the cluster, never on the commands typed, with a threshold of 70.
- Two requirements are blocking: the storefront answers over HTTP, and the kubeconfig has
600permissions.dsoxlab checklists what fails,dsoxlab submitreturns the verdict.