[Oct-2026 Newly Released] CKA Exam Questions For You To Pass [Q42-Q63]

October 14, 2026 admin 0

Rate this post

[Oct-2026 Newly Released] CKA Exam Questions For You To Pass

Linux Foundation CKA Exam: Basic Questions With Answers

Linux Foundation CKA Exam Syllabus Topics:

Section	Weight	Objectives
Topic 1: Cluster Architecture, Installation & Configuration	25%	– Prepare underlying infrastructure for installing a Kubernetes cluster – Implement and configure a highly-available control plane – Use Helm and Kustomize to install cluster components – Understand extension interfaces (CNI, CSI, CRI, etc.) – Manage role based access control (RBAC) – Create and manage Kubernetes clusters using kubeadm – Manage the lifecycle of Kubernetes clusters – Understand CRDs, install and configure operators
Topic 2: Workloads & Scheduling	15%	– Understand Deployments and rolling update/rollback – Understand resource limits and requests – Use label selectors to schedule Pods – Understand how to run multiple schedulers and configure scheduler policies – Understand Static Pods – Use ConfigMaps and Secrets to configure applications – Understand DaemonSets – Understand how scheduler works
Topic 3: Services & Networking	20%	– Use ClusterIP, NodePort, LoadBalancer service types and endpoints – Use the Gateway API to manage Ingress traffic – Understand connectivity between Pods – Know how to use Ingress controllers and Ingress resources – Understand and use CoreDNS – Define and enforce Network Policies
Topic 4: Storage	10%	– Understand how to configure applications with persistent storage – Understand persistent volume claims primitive – Understand Storage Classes and Persistent Volumes – Understand volume mode, access modes and reclaim policies
Topic 5: Troubleshooting	30%	– Troubleshoot application failure – Understand how to monitor applications – Troubleshoot networking – Evaluate cluster and node logging – Troubleshoot cluster component failure – Manage container stdout & stderr logs

QUESTION 42
Create a busybox pod and add “sleep 3600” command

QUESTION 43
For this item, you will havetosshto the nodesik8s-master-0andik8s-node-0and complete all tasks on thesenodes. Ensure that you return tothe base node (hostname:node-1) when you havecompleted this item.
Context
As an administrator of a smalldevelopment team, you have beenasked to set up a Kubernetes clusterto test the viability of a newapplication.
Task
You must usekubeadmto performthis task. Anykubeadminvocationswill require the use of the
–ignore-preflight-errors=alloption.
* Configure thenodeik8s-master-Oas a masternode. .
* Join the nodeik8s-node-otothe cluster.

QUESTION 44
You have a Deployment named ‘api-server’ with 4 replicas of an API server container. You need to implement a rolling update strategy that allows for a maximum of 2 pods to be unavailable at any given time. You also want to ensure that the update process is triggered automatically whenever a new image is pushed to the Docker Hub repository “my.org/api-server:latest’. Furthermore, you want to ensure that the update process is completed within a specified timeout of 5 minutes. If the update fails to complete within the timeout, the deployment should revert to the previous version.

QUESTION 45
Create a pod as follows:
Name: non-persistent-redis
container Image: redis
Volume with name: cache-control
Mount path: /data/redis
The pod should launch in the staging be persistent.

QUESTION 46
Create a deployment called webapp with image nginx having 5 replicas in it, put the file in /tmp directory with named webapp.yaml

//Create a file using dry run command
kubectl create deploy –image=nginx –dry-run -o yaml >
/tmp/webapp.yaml
// Now, edit file webapp.yaml and update replicas=5
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: webapp
name: webapp
spec:
replicas: 5
selector:
matchLabels:
app: webapp
template:
metadata:
labels:
app: webapp
spec:
containers:
– image: nginx
name: nginx
Note: Search “deployment” in kubernetes.io site , you will get
the page
https://kubernetes.io/docs/concepts/workloads/controllers/deplo
yment/
// Verify the Deployment
kubectl get deploy webapp –show-labels
// Output the YAML file of the deployment webapp
kubectl get deploy webapp -o yaml

//Create a file using dry run command
kubectl create deploy –image=nginx –dry-run -o yaml >
/tmp/webapp.yaml
// Now, edit file webapp.yaml and update replicas=5
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: webapp
name: webapp
spec:
replicas: 5
selector:
matchLabels:
app: webapp
template:
metadata:
labels:
Note: Search “deployment” in kubernetes.io site , you will get
the page
https://kubernetes.io/docs/concepts/workloads/controllers/deplo
yment/
// Verify the Deployment
kubectl get deploy webapp –show-labels
// Output the YAML file of the deployment webapp
kubectl get deploy webapp -o yaml

QUESTION 47
List all the pods sorted by name

QUESTION 48
Delete the above pod and create again from the same yaml file
and verifies there is no “test-file.txt” in the path /data/redis
(Since non-persistent storage “emptyDir” is used).

QUESTION 49
List all the pods showing name and namespace with a json path expression See the solution below.

QUESTION 50
List “nginx-dev” and “nginx-prod” pod and delete those pods

QUESTION 51
You have a two-tier application with a frontend service ‘frontend-svc’ exposing a Node.js application running in pods labeled ‘app: frontend’, and a backend service ‘backend-svc’ exposing a Python application running in pods labeled ‘app: backend’. The frontend pods need to communicate with the backend pods through a service. Design a Kubernetes network setup that allows the frontend pods to access the backend service, ensuring that the backend service is reachable only by the frontend service and not directly from outside the cluster.

QUESTION 52
Score:7%

Context
An existing Pod needs to be integrated into the Kubernetes built-in logging architecture (e. g. kubectl logs).
Adding a streaming sidecar container is a good and common way to accomplish this requirement.
Task
Add a sidecar container named sidecar, using the busybox Image, to the existing Pod big-corp-app. The new sidecar container has to run the following command:
/bin/sh -c tail -n+1 -f /va r/log/big-corp-app.log
Use a Volume, mounted at /var/log, to make the log file big-corp-app.log available to the sidecar container.

QUESTION 53
You have a Deployment named ‘my-app’ with 5 replicas running an application container. You need to implement a rolling update strategy that allows for a maximum of 2 pods to be unavailable at any given time during the update process. Additionally, you want to ensure that the update process is triggered automatically whenever a new image is pushed to the Docker Hub repository ‘my.org/my-app:latest’.

QUESTION 54
Check to see how many worker nodes are ready (not including nodes tainted NoSchedule) and write the number to /opt/KUCC00104/kucc00104.txt.

QUESTION 55
Create a busybox pod that runs the command “env” and save the output to “envpod” file

QUESTION 56
You have a Kubernetes cluster with multiple namespaces. You want to create a ClusterRole that grants users in the “admins” group the ability to create, delete, and list Pods in any namespace, but restricts them from managing namespaces themselves.

QUESTION 57
Create an nginx pod which reads username as the environment variable

// create a yml file
kubectl run nginx –image=nginx –restart=Never –dry-run -o
yaml > nginx.yml
// add env section below and create
apiVersion: v1
kind: Pod
metadata:
labels:
run: nginx
name: nginx
spec:
containers:
– image: nginx
name: nginx
env:
– name: USER_NAME
restartPolicy: Never
kubectl create -f nginx.yml
//Verify
kubectl exec -it nginx – env

// create a yml file
kubectl run nginx –image=nginx –restart=Never –dry-run -o
yaml > nginx.yml
// add env section below and create
apiVersion: v1
kind: Pod
metadata:
labels:
run: nginx
name: nginx
spec:
containers:
– image: nginx
name: nginx
env:
– name: USER_NAME
valueFrom:
secretKeyRef:
name: my-secret
key: username
restartPolicy: Never
kubectl create -f nginx.yml
//Verify
kubectl exec -it nginx – env

QUESTION 58
Score: 4%

Task
Scale the deployment presentation to 6 pods.

QUESTION 59
You must connect to the correct host.
Failure to do so may result in a zero score.
[candidate@base] $ ssh Cka000059
Context
A kubeadm provisioned cluster was migrated to a new machine. It needs configuration changes to run successfully.
Task
Fix a single-node cluster that got broken during machine migration.
First, identify the broken cluster components and investigate what breaks them.
The decommissioned cluster used an external etcd server.
Next, fix the configuration of all broken cluster

QUESTION 60
Score: 4%

Task
Schedule a pod as follows:
* Name: nginx-kusc00401
* Image: nginx
* Node selector: disk=ssd

QUESTION 61
You need to create a new role that allows users to create and delete pods, but only in the
‘production’ namespace. How would you define this role using the ‘kubectl’ command?

QUESTION 62
Score: 7%

Task
Create a new NetworkPolicy named allow-port-from-namespace in the existing namespace echo. Ensure that the new NetworkPolicy allows Pods in namespace my-app to connect to port 9000 of Pods in namespace echo.
Further ensure that the new NetworkPolicy:
* does not allow access to Pods, which don’t listen on port 9000
* does not allow access from Pods, which are not in namespace my-app

QUESTION 63
Fix a node that shows as non-ready

Kubectl get nodes
// Check which node shows a not ready
kubectl describe nodes “node-name”
// Login to the node which shows as not ready and check the
process for kubelet, docker , kube-proxy.
// systemctl status kubelet (or) ps -aux | grep -i “processname”
// If the process is not started, then start using
systemctl start kubelet / docker
// Verify
ps -auxxww | grep -i “process-name”
kubectl get nodes

Kubectl get nodes
// Check which node shows a not ready
kubectl describe nodes “node-name”
// Login to the node which shows as not ready and check the
systemctl start kubelet / docker
// Verify
ps -auxxww | grep -i “process-name”
kubectl get nodes