KCNA Container Orchestration Practice Question
What is the purpose of the Container Runtime Interface (CRI) in Kubernetes?
⚠ Common exam trap
A common misconception is that CRI is a cross-platform API for container orchestration, when in fact it is a Kubernetes-specific interface designed solely to abstract the container runtime from the kubelet.
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
✓
To allow kubelet to use different container runtimes without modifying its code
The Container Runtime Interface (CRI) is a plugin interface that enables the kubelet to use a wide variety of container runtimes without requiring changes to the core Kubernetes code. By defining a standard set of gRPC APIs for runtime operations (like pod and container lifecycle management), CRI decouples the kubelet from any specific runtime implementation, allowing runtimes like containerd, CRI-O, and Docker (via dockershim, now deprecated) to be used interchangeably.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
To allow kubelet to use different container runtimes without modifying its code
Why this is correct
CRI abstracts the container runtime so that kubelet can work with containerd, CRI-O, etc.
- ✗
To replace Docker as the only supported runtime
Why it's wrong here
CRI does not replace Docker; it enables multiple runtimes. Docker was deprecated as a runtime but can still be used via dockershim (removed in v1.24).
- ✗
To define the format of container images
Why it's wrong here
Image format is defined by the OCI Image Spec, not CRI.
- ✗
To provide a standard API for managing containers across different orchestration platforms
Why it's wrong here
CRI is specific to Kubernetes, not a general cross-platform API.
Go deeper
Related to this question
Learn chapter
Kubernetes Overview and Core Components
Key term
ReplicaSet and Replication
A ReplicaSet ensures a specified number of identical pod instances are running at all times in Kubernetes, using replication to maintain availability and stability.
Key term
Container Runtime Interface
The Container Runtime Interface (CRI) is a standardized plugin protocol that allows Kubernetes to work with different container runtimes without needing to change its core code.
About these practice questions
This KCNA question is part of Courseiva's 833-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
5 more ways this is tested on KCNA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. What is the primary purpose of the Container Runtime Interface (CRI) in Kubernetes?
easy- A.To store container images in a registry
- B.To define the format of container images
- C.To manage container network interfaces
- ✓ D.To provide a standard interface between the kubelet and container runtimes
Why D: The Container Runtime Interface (CRI) is a plugin protocol that enables the kubelet to use any OCI-compliant container runtime (e.g., containerd, CRI-O) without needing to recompile Kubernetes. It defines gRPC APIs for runtime and image service operations, abstracting the runtime implementation from the kubelet's pod lifecycle management.
Variation 2. What is the purpose of the Container Runtime Interface (CRI) in Kubernetes?
easy- ✓ A.To allow kubelet to use different container runtimes
- B.To manage persistent storage for containers
- C.To provide a network plugin interface for pods
- D.To define a standard for container images
Why A: The Container Runtime Interface (CRI) is a plugin interface that enables the kubelet to use a variety of container runtimes without needing to recompile the Kubernetes source code. By defining a standard API (gRPC-based) for runtime operations like pulling images and managing containers, CRI decouples Kubernetes from specific runtime implementations such as containerd, CRI-O, or Docker (via dockershim). This abstraction allows cluster administrators to choose the most suitable runtime for their environment while maintaining compatibility with the Kubernetes control plane.
Variation 3. What is the purpose of the Container Runtime Interface (CRI)?
easy- A.To manage container networking
- B.To define a standard for container images
- C.To orchestrate multi-container pods
- ✓ D.To allow kubelet to communicate with different container runtimes
Why D: The Container Runtime Interface (CRI) is a plugin interface that enables the kubelet to use a variety of container runtimes without needing to recompile the Kubernetes components. It defines the API for creating, starting, stopping, and deleting containers, allowing the kubelet to communicate with runtimes like containerd, CRI-O, or Docker (via dockershim, now deprecated). Option D is correct because the CRI's primary purpose is to abstract the runtime implementation from the kubelet, enabling interoperability.
Variation 4. What is the Container Runtime Interface (CRI)?
easy- ✓ A.A plugin interface that allows kubelet to use a variety of container runtimes
- B.A specification for container images
- C.A registry for storing container images
- D.A command-line tool for managing containers
Why A: The Container Runtime Interface (CRI) is a plugin interface that enables the kubelet to communicate with different container runtimes (e.g., containerd, CRI-O) without needing to know their internal implementation details. It defines a gRPC-based protocol for managing container lifecycles, image operations, and pod sandboxes, allowing Kubernetes to remain runtime-agnostic.
Variation 5. What is the Container Runtime Interface (CRI)?
easy- A.A tool for building container images
- B.A standard for container runtime logs
- C.A specification for container images
- ✓ D.An API between kubelet and container runtime
Why D: The Container Runtime Interface (CRI) is a plugin interface that enables the kubelet to use a variety of container runtimes without needing to recompile the kubelet. It defines a gRPC API (protocol buffers) for the kubelet to communicate with the container runtime, covering operations like pod lifecycle management and image management. Option D correctly identifies this as the API between the kubelet and the container runtime.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This KCNA 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 KCNA exam.