---
id: act-04-kubernetes-intro-understanding
title: Kubernetes Intro - Understanding
mode: understanding
open_at: 2026-02-01T00:00:00+01:00
close_at: 2026-12-31T23:59:59+01:00
retakes_enabled: true
max_attempts: 999
grade_max: 100
---

## T1
Type: mcq
Points: 20
Prompt: Which description best matches what Kubernetes does?
Refs:
- mat-06-kubernetes-intro#what-kubernetes-is
- mat-06-kubernetes-intro#orchestration
Choices:
- [x] It deploys applications and can scale, self-heal, and manage rollouts/rollbacks.
- [ ] It is a programming language for writing cloud-native applications.
- [ ] It is a container image format used to distribute applications.
- [ ] It is a single server operating system kernel.

## T2
Type: short
Points: 15
Prompt: What does the abbreviation K8s mean?
Refs:
- mat-06-kubernetes-intro#whats-in-the-name-and-k8s
Answer: The 8 replaces the eight letters between K and s in Kubernetes.

## T3
Type: single_choice
Points: 20
Prompt: For high availability, which control plane sizing is recommended? A) 1 control plane node B) 2 control plane nodes C) 3 or 5 control plane nodes D) 7 control plane nodes
Refs:
- mat-06-kubernetes-intro#control-plane-nodes-and-worker-nodes

## T4
Type: multiple_choice
Points: 25
Prompt: Which items are part of the control plane services described in the material? A) API server B) Scheduler C) Cluster store (etcd) D) Kubelet E) Controller manager/controllers F) Kube-proxy
Refs:
- mat-06-kubernetes-intro#control-plane-services
- mat-06-kubernetes-intro#worker-node-components

## T5
Type: essay
Points: 20
Prompt: Explain Kubernetes' declarative model using desired state, observed state, and reconciliation, and contrast it with an imperative approach using one concrete example (failure recovery or an update).
Refs:
- mat-06-kubernetes-intro#desired-state-observed-state-and-reconciliation
- mat-06-kubernetes-intro#declarative-versus-imperative
- mat-06-kubernetes-intro#self-healing-and-rolling-updates-example
Rubric:
- Defines desired state, observed state, and reconciliation correctly. (8)
- Describes the YAML->API server->cluster store flow and the role of controllers/watch loops. (6)
- Provides a concrete example (replica self-heal or image update) and contrasts with imperative scripting. (6)