Nov-2025 Pass Your CKA Exam at the First Try with 100% Real Exam
Get Real Exam Questions for CKA with New Questions
NEW QUESTION # 29
Create a pod named kucc8 with a single app container for each of the
following images running inside (there may be between 1 and 4 images specified):
nginx + redis + memcached.
Answer:
Explanation:
See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\5 B.JPG
F:\Work\Data Entry Work\Data Entry\20200827\CKA\5 C.JPG
F:\Work\Data Entry Work\Data Entry\20200827\CKA\5 D.JPG
NEW QUESTION # 30
Score: 4%
Task
Create a persistent volume with name app-data , of capacity 1Gi and access mode ReadOnlyMany. The type of volume is hostPath and its location is /srv/app-data .
Answer:
Explanation:
Solution:
#vi pv.yaml
apiVersion: v1
kind: PersistentVolume
metadata:
name: app-config
spec:
capacity:
storage: 1Gi
accessModes:
- ReadOnlyMany
hostPath:
path: /srv/app-config
#
kubectl create -f pv.yaml
NEW QUESTION # 31
Your Kubernetes cluster is experiencing slow deployments, and you suspect that the image pull process is causing the bottleneck. You need to investigate the image pull performance and optimize it to speed up deployments.
Answer:
Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Identify the Slow Deployments:
- Monitor the deployment progress for recent deployments using 'kubectl rollout status deployment '
- Identify the deployments that are experiencing slow image pulls.
2. Examine Deployment Logs:
- Check the deployment logs for messages related to image pulling.
- You can view logs using 'kubectl logs -f.
- Look for messages like "Pulling image" and "Image pull timed out" to identify pods that are experiencing slow image pulls.
3. Check Image Registry Connectivity:
- Verify that the pods can connect to the image registry:
- Run 'kubectl exec -it -n bash' to enter a pod in the deployment.
- Use 'ping to check network connectivity to the image registry.
- If connectivity is an issue, resolve any network problems between the pods and the image registry.
4. Verify Image Registry Credentials:
- Ensure the pods have the correct credentials to access the image registry.
- Check if the credentials are stored in a secret and mounted into the pod's service account.
- If necessary, create a new secret with the correct credentials for the image registry.
5. Optimize Image Pull Policy:
- Set the 'imagePullPolicy' to 'Always' in the deployment YAML:
- This ensures that the pods always pull the latest image from the registry, avoiding potential caching issues.
7. Optimize Network Bandwidth: - Ensure sufficient network bandwidth is available for image pulls: - Check the network connection between the nodes and the image registry. - Consider using a dedicated network connection for image pulls if possible. 8. Use Image Caching: - Enable image caching on the nodes to reduce image pull times: - Many container registries offer image caching features. - Configure the image cache to store frequently used images locally on the nodes. 9. Monitor Deployment Performance: - After making changes to the deployment configuration, monitor the performance of deployments: - Check the deployment logs and use 'kubectl rollout status deployment to verify that deployments are completing faster. 10. Consider Alternative Approaches: - If the image pull performance remains slow, consider these alternative approaches: - Pre-pull images: Download the required images to a local image repository before deployment. - Use image-based deployments: Deploy container images directly instead of using a deployment. - Employ a dedicated image puller: Use a separate container or service to handle image pulls.,
NEW QUESTION # 32
Create a pod with environment variables as var1=value1.Check the environment variable in pod
- A. kubectl run nginx --image=nginx --restart=Never --env=var1=value1
# then
kubectl exec -it nginx -- env
# or
kubectl describe po nginx | grep value1 - B. kubectl run nginx --image=nginx --restart=Never --env=var1=value1
# then
kubectl exec -it nginx -- env
# or
kubectl exec -it nginx -- sh -c 'echo $var1'
# or
kubectl describe po nginx | grep value1
Answer: B
NEW QUESTION # 33
Score: 4%
Task
Check to see how many nodes are ready schedulable (not including nodes tainted NoSchedule ) and write the number to /opt/KUSC00402/kusc00402.txt.
Answer:
Explanation:
Solution:
kubectl describe nodes | grep ready|wc -l
kubectl describe nodes | grep -i taint | grep -i noschedule |wc -l
echo 3 > /opt/KUSC00402/kusc00402.txt
#
kubectl get node | grep -i ready |wc -l
# taints#noSchedule
kubectl describe nodes | grep -i taints | grep -i noschedule |wc -l
#
echo 2 > /opt/KUSC00402/kusc00402.txt
NEW QUESTION # 34
Create a deployment as follows:
Name: nginx-random
Exposed via a service nginx-random
Ensure that the service & pod are accessible via their respective DNS records The container(s) within any pod(s) running as a part of this deployment should use the nginx Image Next, use the utility nslookup to look up the DNS records of the service & pod and write the output to
/opt/KUNW00601/service.dns and /opt/KUNW00601/pod.dns respectively.
Answer:
Explanation:
See the solution below.
Explanation
Solution:
F:\Work\Data Entry Work\Data Entry\20200827\CKA\17 C.JPG
F:\Work\Data Entry Work\Data Entry\20200827\CKA\17 D.JPG
F:\Work\Data Entry Work\Data Entry\20200827\CKA\17 E.JPG
NEW QUESTION # 35
Score: 4%
Task
Schedule a pod as follows:
* Name: nginx-kusc00401
* Image: nginx
* Node selector: disk=ssd
Answer:
Explanation:
Solution:
#yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx-kusc00401
spec:
containers:
- name: nginx
image: nginx
imagePullPolicy: IfNotPresent
nodeSelector:
disk: spinning
#
kubectl create -f node-select.yaml
NEW QUESTION # 36
Score: 4%
Task
Schedule a pod as follows:
* Name: nginx-kusc00401
* Image: nginx
* Node selector: disk=ssd
Answer:
Explanation:
See the solution below.
Explanation
Solution:
#yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx-kusc00401
spec:
containers:
- name: nginx
image: nginx
imagePullPolicy: IfNotPresent
nodeSelector:
disk: spinning
#
kubectl create -f node-select.yaml
NEW QUESTION # 37
A Kubernetes worker node, named wk8s-node-0 is in state NotReady. Investigate why this is the case, and perform any appropriate steps to bring the node to a Ready state, ensuring that any changes are made permanent.
You can ssh to the failed node using:
[student@node-1] $ | ssh Wk8s-node-0
You can assume elevated privileges on the node with the following command:
[student@w8ks-node-0] $ | sudo -i
Answer:
Explanation:
solution
NEW QUESTION # 38
Create a busybox pod that runs the command "env" and save the output to "envpod" file See the solution below.
Answer:
Explanation:
kubectl run busybox --image=busybox --restart=Never --rm -it -- env > envpod.yaml
NEW QUESTION # 39
From the pod labelname=cpu-utilizer, find podsrunning high CPU workloads and write the name of the pod consumingmost CPU to thefile/opt/KUTR00102/KUTR00102.txt(which already exists).
Answer:
Explanation:
See the solution below.
Explanation
solution
NEW QUESTION # 40
Create a deployment spec file that will:
* Launch 7 replicas of the nginx Image with the labelapp_runtime_stage=dev
* deployment name: kual00201
Save a copy of this spec file to /opt/KUAL00201/spec_deployment.yaml
(or /opt/KUAL00201/spec_deployment.json).
When you are done, clean up (delete) any new Kubernetes API object that you produced during this task.
Answer:
Explanation:
NEW QUESTION # 41
From the pod label name=cpu-utilizer, find pods running high CPU workloads and write the name of the pod consuming most CPU to the file /opt/KUTR00102/KUTR00102.txt (which already exists).
Answer:
Explanation:
solution
NEW QUESTION # 42
You have a Deployment running on a Kubernetes cluster with limited resources. How can you adjust the Deployment to use resources more efficiently and prevent resource contention?
Answer:
Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Define Resource Requests and Limits:
- Set 'requests' and 'limits' for CPU and memory for the containers in the Deployment.
- This helps in specifying the minimum resources required by the pods and the maximum resources that they can consume.
2. Optimize Container Images: - Use smaller and more efficient container images to reduce the resource footprint of the pods. 3. Use Resource Quotas: - Apply resource quotas at the namespace level to control the resource consumption of the pods within a namespace. 4. Consider Pod Disruption Budgets (PDB): - Implement PDBs to control the maximum number of pods that can be unavailable during a rolling update or pod deletion. - This ensures that the application remains available during resource-intensive events. 5. Utilize Node Affinity and Tolerations: - Configure node affinity and tolerations to schedule pods on specific nodes that have the required resources. 6. Monitor Resource Utilization: - Regularly monitor the resource utilization of the cluster and the pods. - Use tools like 'kubectl top pods', 'kubectl top nodes', and 'kubectl describe nodes' to gather resource utilization data. - Adjust resource requests and limits accordingly based on the monitoring data.
NEW QUESTION # 43
Score: 7%
Task
Reconfigure the existing deployment front-end and add a port specification named http exposing port 80/tcp of the existing container nginx.
Create a new service named front-end-svc exposing the container port http.
Configure the new service to also expose the individual Pods via a NodePort on the nodes on which they are scheduled.
Answer:
Explanation:
Solution:
kubectl get deploy front-end
kubectl edit deploy front-end -o yaml
#port specification named http
#service.yaml
apiVersion: v1
kind: Service
metadata:
name: front-end-svc
labels:
app: nginx
spec:
ports:
- port: 80
protocol: tcp
name: http
selector:
app: nginx
type: NodePort
# kubectl create -f service.yaml
# kubectl get svc
# port specification named http
kubectl expose deployment front-end --name=front-end-svc --port=80 --tarport=80 --type=NodePort
NEW QUESTION # 44
Deploy a pod with image=redis on a node with label disktype=ssd
- A. // Get list of nodes
kubectl get nodes
//Get node with the label disktype=ssd
kubectl get no -l disktype=ssd
// Create a sample yaml file
kubectl run node-redis --generator=run-pod/v1 --image=redis --dry
run -o yaml > test-redis.yaml
// Edit test-redis.yaml file and add nodeSelector
vim test-redis.yaml
apiVersion: v1
- name: node-redis
image: redis
imagePullPolicy: IfNotPresent
kubectl apply -f test-redis.yaml
/ // Verify
K kubectl get po -o wide - B. // Get list of nodes
kubectl get nodes
//Get node with the label disktype=ssd
kubectl get no -l disktype=ssd
// Create a sample yaml file
kubectl run node-redis --generator=run-pod/v1 --image=redis --dry
run -o yaml > test-redis.yaml
// Edit test-redis.yaml file and add nodeSelector
vim test-redis.yaml
apiVersion: v1
kind: Pod
metadata:
name: redis
spec:
nodeSelector:
disktype: ssd
containers:
- name: node-redis
image: redis
imagePullPolicy: IfNotPresent
kubectl apply -f test-redis.yaml
/ // Verify
K kubectl get po -o wide
Answer: B
NEW QUESTION # 45
Get list of persistent volumes and persistent volume claim in the cluster
Answer:
Explanation:
kubectl get pv kubectl get pvc
NEW QUESTION # 46
Create a pod that echo "hello world" and then exists. Have the pod deleted automatically when it's completed
Answer:
Explanation:
kubectl run busybox --image=busybox -it --rm --restart=Never --
/bin/sh -c 'echo hello world'
kubectl get po # You shouldn't see pod with the name "busybox"
NEW QUESTION # 47
Schedule a pod as follows:
* Name: nginx-kusc00101
* Image: nginx
* Node selector: disk=ssd
Answer:
Explanation:
See the solution below.
Explanation
solution
NEW QUESTION # 48
You have a Deployment for a web application named 'web-app-deployment' that uses an image named 'web-app:vl .0'. You want to implement a rolling update to upgrade the deployment to a new version, 'web-app:v2.0', but only allow a maximum of 2 pods to be unavailable at any time during the update. How would you achieve this using Kubernetes?
Answer:
Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Update the Deployment YAML:
- Open the Deployment YAML file for 'web-app-deployment' (e.g., 'web-app-deployment.yaml').
- Modify the 'image' field within the 'spec.template.spec.containers' section to the new image: 'web-app:v2.0'.
- Adjust the 'strategy.rollingUpdate' section to control the rolling update process:
- Set 'maxUnavailable: 2' to allow a maximum of 2 pods to be unavailable at any time.
- Keep 'maxSurge: 0' if you don't want additional pods to be created during the update.
2. Apply the Updated Deployment: - IJse 'kubectl apply -f web-app-deployment.yaml' to apply the updated Deployment YAML. 3. Monitor the Rolling Update: - Use 'kubectl get pods -l app=web-app' to monitor the update process. You will see that Kubernetes will gradually terminate old pods running 'web-app:vl .0' and create new pods with 'web-app:v2.0'. - You can also use "kubectl describe deployment web-app-deployment' to observe the progress of the rolling update. 4. Verify Successful Update: - Once the update is complete, confirm that all pods are running the new image 'web-app:v2.0'. You can check the output of 'kubectl get pods -l app=web-app' or 'kubectl describe deployment web-app-deployment'.
NEW QUESTION # 49
Score: 4%
Task
Schedule a pod as follows:
* Name: nginx-kusc00401
* Image: nginx
* Node selector: disk=ssd
Answer:
Explanation:
Solution:
#yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx-kusc00401
spec:
containers:
- name: nginx
image: nginx
imagePullPolicy: IfNotPresent
nodeSelector:
disk: spinning
#
kubectl create -f node-select.yaml
NEW QUESTION # 50
......
Updated CKA Certification Exam Sample Questions: https://exams4sure.pdftorrent.com/CKA-latest-dumps.html