CKA Practice Question: Cluster Architecture, Installation and Configuration
Which command is used to initialize a Kubernetes cluster using kubeadm?
⚠ Common exam trap
Candidates often confuse `kubeadm init` with non-existent commands like `kubeadm create cluster` or `kubeadm bootstrap`, assuming a more intuitive or verbose command exists, when in fact kubeadm's subcommands are deliberately minimal and specific.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
kubeadm init
The correct command to initialize a Kubernetes cluster using kubeadm is `kubeadm init`. This command performs the bootstrap process by setting up the control plane components (e.g., API server, etcd, controller manager, scheduler) on the node, generating certificates, and creating the necessary configuration files in `/etc/kubernetes/`. It is the standard first step after installing kubeadm, kubelet, and a container runtime.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
kubeadm init
Why this is correct
kubeadm init is the correct command because it initializes a Kubernetes control-plane node, performing preflight checks, generating PKI certificates, kubeconfig files, and etcd cluster configuration. It is the standard bootstrap mechanism for building a new cluster and is the only valid 'initialization' subcommand in kubeadm's CLI.
- ✗
kubeadm create cluster
Why it's wrong here
The command 'kubeadm create cluster' does not exist in kubeadm's command set. kubeadm's primary verbs are 'init' to bootstrap a control-plane, 'join' to add worker or control-plane nodes, and 'reset' to remove a node. There is no 'create' subcommand; the Kubernetes documentation and kubeadm help output never reference such a command.
- ✗
kubeadm start
Why it's wrong here
'kubeadm start' is invalid because kubeadm is not a service manager; it is a cluster bootstrap toolkit. The verb 'start' is typically used with systemctl for starting daemons like kubelet, but kubeadm's job is to initialize or join nodes, not to start services. Running 'kubeadm start' would produce an error, as no such subcommand is defined.
- ✗
kubeadm bootstrap
Why it's wrong here
'kubeadm bootstrap' is not a valid subcommand, although 'bootstrap' is a relevant concept in Kubernetes (e.g., bootstrap tokens used for TLS discovery during 'kubeadm join'). The actual command to initialize a cluster is 'kubeadm init', not 'bootstrap'. Since this is a common misconception, note that kubeadm uses 'init' and 'join' as its primary actions.
Go deeper
Related to this question
Learn chapter
Kubernetes Architecture Overview
Key term
Ingress Resources
Ingress Resources are Kubernetes API objects that manage external access to services inside a cluster, typically HTTP and HTTPS traffic, by defining rules for routing requests based on hostnames and paths.
Key term
Container Runtime
A container runtime is software that runs containers by using the host operating system's kernel to isolate processes, manage filesystem layers, and handle networking.
About these practice questions
One of 302 original CKA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKA exam.