Free practice · No sign-up required
15 questions with answer explanations. Choose an answer below to begin.
Which resource is used to define how to run a single container process in Kubernetes?
Understand core workload resources and their purposes.
0/15 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.
Learn by doing
Use official documentation and hands-on labs to work through topics you missed.
Application examples from the Kubernetes project for practicing manifests and application behavior in a cluster.
Try it: Use a disposable cluster. Read a simple application's manifests, predict which Pods its Service selects, then change a label and use kubectl to diagnose the resulting connectivity problem.
Source is free. A local cluster uses your computer; hosted clusters may incur charges.
Guided tutorials for learning Kubernetes behavior and building practical skills beyond multiple-choice recall.
Try it: Complete a basic application tutorial. Repeat the task without the walkthrough, then explain the difference between declared configuration and observed cluster state.
Documentation is free. Your chosen cluster environment may have costs.
Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.
Which resource is used to define how to run a single container process in Kubernetes?
Pod
Deployment
Service
ConfigMap
Correct answer
Pod
A Pod is the smallest deployable unit in Kubernetes and defines how to run one or more containers. It is the basic execution unit for containerized applications.
Which command retrieves the logs from a running container in a Pod?
kubectl logs
kubectl describe
kubectl get
kubectl exec
Correct answer
kubectl logs
The kubectl logs command is used to fetch logs from a container inside a Pod. It supports retrieving logs from a single container or all containers in the Pod.
What is the purpose of a Kubernetes Service of type ClusterIP?
Exposes the service internally within the cluster
Exposes the service externally via a cloud provider load balancer
Exposes the service on a static port on each node
Exposes the service to the internet via DNS
Correct answer
Exposes the service internally within the cluster
ClusterIP is the default service type and provides a stable internal IP address for communication within the cluster. It is not reachable from outside the cluster.
Which resource definition allows you to inject environment variables from a ConfigMap into a container?
envFrom
volumeMounts
livenessProbe
securityContext
Correct answer
envFrom
The envFrom field in a container specification can reference a ConfigMap to inject all its keys as environment variables. This helps manage configuration without changing container images.
What is the main difference between a ReplicaSet and a Deployment?
Deployment provides declarative updates to Pods, while ReplicaSet does not
ReplicaSet supports rolling updates, while Deployment does not
Deployment manages network policies, while ReplicaSet manages storage
ReplicaSet is used for stateful workloads, while Deployment is for batch jobs
Correct answer
Deployment provides declarative updates to Pods, while ReplicaSet does not
A Deployment is a higher-level controller that manages ReplicaSets and provides declarative updates, rollbacks, and scaling for Pods. ReplicaSet ensures a specified number of pod replicas are running.
Which kubectl command helps you debug connectivity issues between Pods?
kubectl run
kubectl debug
kubectl describe
kubectl port-forward
Correct answer
kubectl debug
kubectl debug allows you to create debugging containers alongside an existing Pod to inspect networking and filesystem issues. It is useful for troubleshooting connectivity and configuration problems.
What does a readiness probe determine?
Whether the container is healthy and should receive traffic
Whether the container has started successfully
Whether the node has enough resources
Whether the Pod should be restarted
Correct answer
Whether the container is healthy and should receive traffic
A readiness probe indicates whether a container is ready to accept traffic. If it fails, the Pod is removed from Service endpoints until it passes.
Which field in a Pod spec defines resource requests and limits?
resources
spec
containers
limits
Correct answer
resources
The resources field under a container specification defines requests and limits for CPU and memory. This helps the scheduler make placement decisions and manage resource usage.
What is the role of a PersistentVolumeClaim in Kubernetes?
It requests storage resources on behalf of a Pod
It formats the underlying disk device
It defines network policies for storage traffic
It creates a backup of container data
Correct answer
It requests storage resources on behalf of a Pod
A PersistentVolumeClaim is a request for storage by a user. It allows Pods to consume persistent storage without knowing the details of the underlying storage infrastructure.
Which Kubernetes object is used to store sensitive information such as passwords?
Secret
ConfigMap
Volume
Environment
Correct answer
Secret
Secrets are designed to hold sensitive data like passwords, tokens, and keys. They are base64-encoded and stored separately from Pod definitions to improve security.
What is the purpose of a liveness probe?
To determine if a container should be restarted
To expose the container to external traffic
To set resource limits for the container
To mount a persistent volume
Correct answer
To determine if a container should be restarted
A liveness probe checks if a container is still running. If it fails, the kubelet restarts the container. It helps recover from deadlocks or unhealthy states.
Which resource is best suited for running a batch job that completes after processing a queue?
Job
Deployment
DaemonSet
StatefulSet
Correct answer
Job
A Job is designed to run one or more pods to completion, making it ideal for batch processing tasks. It ensures the specified number of Pods successfully terminate.
What does a NodePort service do?
Exposes the service on a static port on each cluster node
Routes traffic based on DNS names
Provides an internal load balancer
Restricts access to specific IP ranges
Correct answer
Exposes the service on a static port on each cluster node
A NodePort service opens a specific port on all nodes in the cluster and forwards traffic to the service. It allows external access using :.
Which command is used to apply a configuration file to create or update resources?
kubectl apply
kubectl create
kubectl run
kubectl replace
Correct answer
kubectl apply
kubectl apply performs a declarative update of resources by comparing the configuration file with the live state and reconciling differences. It is the recommended way to manage configurations.
What is the primary use of an init container?
To run setup or utility tasks before the main application starts
To replace the main container if it crashes
To monitor the main container's performance
To provide network connectivity to the Pod
Correct answer
To run setup or utility tasks before the main application starts
Init containers run to completion before the main application containers start. They are useful for tasks like loading configuration, waiting for dependencies, or preparing data.
Recall the answer before opening each card.
A Pod. It defines how to run one or more containers and is the basic execution unit for containerized applications.
kubectl logs. It retrieves logs from a single container or all containers in a Pod.
ClusterIP. It provides a stable internal IP reachable only within the cluster.
Use the envFrom field in the container spec referencing the ConfigMap. It injects all key-value pairs as environment variables.
Deployment provides declarative updates, rollbacks, and scaling. ReplicaSet only ensures a specified number of pods are running.
kubectl debug. It adds a temporary container to help inspect networking and filesystem issues.
Whether the container is ready to accept traffic. If it fails, the Pod is removed from Service endpoints.
Under the resources field within the container specification. It includes CPU and memory requests and limits.
It requests storage resources on behalf of a Pod, abstracting the underlying storage infrastructure.
Secret. It holds sensitive information base64-encoded and is stored separately from Pod definitions.
It checks if a container is still running. On failure, the kubelet restarts the container to recover from unhealthy states.
Job. It runs one or more pods to completion, making it ideal for batch tasks.
It exposes the service on a static port on each cluster node, allowing external access via : .
kubectl apply. It reconciles the live state with the provided configuration file.
To run setup or utility tasks before the main application starts, such as waiting for dependencies or preparing data.
ConfigMap stores data in plain text; Secret stores data base64-encoded. Secrets are intended for sensitive information.
ReplicaSet does not support declarative updates; you must manually update its template. Deployment handles rolling updates and rollbacks automatically.
The Pod is removed from the Service's endpoints until the probe passes again. It does not restart the container.
Mount the claim as a volume in the Pod spec using the volumes and volumeMounts fields. The Pod then reads/writes to persistent storage.
apply is declarative and updates resources without error if they exist; create is imperative and fails if the resource already exists. apply is recommended for config management.
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Connect the concepts
Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
This section focuses on the core building blocks for running containers: Pods, Deployments, ReplicaSets, Jobs, and init containers. Understanding when to use each resource is critical for application developers. Pods are the smallest unit, Deployments provide declarative updates, ReplicaSets ensure replica count, Jobs run to completion, and init containers perform setup tasks. Probes (liveness and readiness) are essential for managing container health and traffic flow.
Managing configuration and sensitive data separately from container images is a key CKAD skill. ConfigMaps and Secrets allow you to inject environment variables, files, or command-line arguments. PersistentVolumeClaims enable pods to request persistent storage without knowing underlying storage details. The envFrom field simplifies injecting all keys from a ConfigMap or Secret into a container's environment.
Kubernetes networking enables communication between pods and external clients. Services abstract pod IPs and provide stable endpoints. ClusterIP exposes a service internally, while NodePort opens a static port on all nodes for external access. Understanding service types and when to use them is crucial for exposing applications correctly.
Developers must be proficient in troubleshooting and optimizing resources. kubectl logs retrieves container logs, kubectl debug creates debugging containers alongside pods. Resource requests and limits (CPU/memory) help the scheduler place pods and prevent resource starvation. kubectl apply manages resources declaratively, making it the recommended method for production configurations.
Study workflow
Create a ConfigMap with key-value pairs. Then define a Pod that references the ConfigMap using envFrom. Apply the Pod YAML with kubectl apply. Verify that environment variables are injected by exec'ing into the container and running env.
Create a Deployment for your app. Create a NodePort Service targeting the deployment's selector. Check service details with kubectl get svc. Access the application using any node's IP and the assigned NodePort.
Add an HTTP readiness probe and a liveness probe to your Pod spec. Use endpoints like /healthz. Apply the Pod. Observe probe failures with kubectl describe pod. Note removal from Service endpoints on readiness failure and container restart on liveness failure.
If a pod is not working, use kubectl debug mypod -it --image=busybox --copy-to=mydebugger. This creates a temporary container alongside the original pod. Use tools like curl or netstat to inspect network connectivity and filesystem.
Create a PersistentVolumeClaim requesting 1Gi of storage. In a Pod spec, mount the PVC at a path. The Pod will use the claim to access persistent storage. Check that data persists across pod restarts by writing a file and recreating the pod.
FAQ
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
ConfigMaps store non-confidential configuration data in plain text, while Secrets are intended for sensitive data (e.g., passwords, tokens). Secrets are base64-encoded and can be further encrypted at rest. Both can be injected as environment variables or mounted as volumes.
Use a Job for tasks that run to completion, like batch processing or database migrations. Deployments are for long-running services that should stay up. Jobs ensure a specified number of pods successfully terminate, making them ideal for finite workloads.
Use ClusterIP for internal microservice communication; it is not reachable externally. Use NodePort when you need external access, such as for development or when a load balancer is not available. NodePort opens a static port on every node.
A liveness probe checks if a container is still running. If it fails, the kubelet restarts the container. This helps recover from deadlocks or application hangs. It is separate from readiness probes, which control traffic routing.
Yes, kubectl apply updates the resource declaratively. It compares the provided configuration with the live state and applies changes accordingly. This is the recommended method for managing resources in production, as it supports drift correction and works well with GitOps workflows.
Browse another free bank or use the study strategy guide to turn your misses into spaced review.
