Get Ready to Pass the CKA exam with Linux Foundation Latest Practice Exam [Q50-Q68]

4/5 - (1 vote)

Get Ready to Pass the CKA exam with Linux Foundation Latest Practice Exam

Get Prepared for Your CKA Exam With Actual Linux Foundation Study Guide!

Linux Foundation CKA Exam Syllabus Topics:

Section	Weight	Objectives
Topic 1: Services & Networking	20%	– Services (ClusterIP, NodePort, LoadBalancer) – Network policies – Ingress configuration
Topic 2: Cluster Architecture, Installation & Configuration	25%	– Kubernetes architecture components – Cluster installation and configuration – High availability setup
Topic 3: Storage	10%	– PersistentVolumes and PersistentVolumeClaims – Storage classes
Topic 4: Troubleshooting	30%	– Application and networking debugging – Cluster component troubleshooting
Topic 5: Workloads & Scheduling	15%	– Deployments and rolling updates – Scheduling constraints – ConfigMaps and Secrets

QUESTION 50
You are running a stateful application using a StatefulSet. How do you ensure that the application data is preserved during a rolling update?

QUESTION 51
You have a StatefulSet named ‘database-statefulset’ that runs a database service. The database requires persistent data storage. You are experiencing a problem where the database pods are crashing repeatedly, and the database data is getting lost. You suspect that there is an issue with the persistent volume claim (PVC) used by the StatefulSet. How would you troubleshoot and potentially fix this problem?

QUESTION 52
Check the Image version of nginx-dev pod using jsonpath

QUESTION 53
Score: 4%

Task
Set the node named ek8s-node-1 as unavailable and reschedule all the pods running on it.

QUESTION 54
Deploy a pod with image=redis on a node with label disktype=ssd

// 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

// 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

QUESTION 55
Create a pod with init container which waits for a service called “myservice” to be created. Once init container completes, the myapp-container should start and print a message “The app is running” and sleep for 3600 seconds.

vim multi-container-pod.yaml
apiVersion: v1
kind: Pod
metadata:
name: myapp-pod
labels:
app: myapp
spec:
containers:
– name: myapp-container
image: busybox:1.28
command: [‘sh’, ‘-c’, ‘echo The app is running! && sleep
3600′]
initContainers:
– name: init-myservice
done”]
// Check whether service called “myservice” exists
kubectl get svc
Note: Pod will not start if service called “myservice” doesn’t
exist.
// Now, Create the pod
kubectl apply -f multi-container-pod.yaml

vim multi-container-pod.yaml
apiVersion: v1
kind: Pod
metadata:
name: myapp-pod
labels:
app: myapp
spec:
containers:
– name: myapp-container
image: busybox:1.28
command: [‘sh’, ‘-c’, ‘echo The app is running! && sleep
3600′]
initContainers:
– name: init-myservice
image: busybox:1.28
command: [‘sh’, ‘-c’, “until nslookup myservice.$(cat
/var/run/secrets/kubernetes.io/serviceaccount/namespace).s
vc.cluster.local; do echo waiting for myservice; sleep 2;
done”]
// Check whether service called “myservice” exists
kubectl get svc
Note: Pod will not start if service called “myservice” doesn’t
exist.
// Now, Create the pod
kubectl apply -f multi-container-pod.yaml

QUESTION 56
You are managing a Kubernetes cluster for a company with multiple teams working on different projects. You want to implement RBAC to ensure each team has access only to the resources they need.

QUESTION 57
You have a Deployment running a web application that receives a significant amount of traffic. You need to implement a strategy to scale the Deployment based on the traffic load while ensuring that the application remains available during the scaling process.

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

QUESTION 59
Score: 4%

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

QUESTION 60
You are working with a Kubernetes cluster that has been configured with RBAC. You need to create a deployment for a new application, but you are encountering permission issues. You have verified that your user account belongs to the “developers” group, which should have sufficient permissions to create deployments. However, you are receiving an error message indicating insufficient privileges.
Investigate the potential causes for the permission issue and provide solutions to resolve the problem.

QUESTION 61
List all the pods showing name and namespace with a json path expression

QUESTION 62
Create a ETCD backup of kubernetes cluster
Note : You don’t need to memorize command, refer –
https://kubernetes.io/docs/tasks/administer-cluster/configureupgrade-etcd/ during exam

ETCDCTL_API=3 etcdctl –endpoints=[ENDPOINT] –cacert=[CA CERT]
–cert=[ETCD SERVER CERT] –key=[ETCD SERVER KEY] snapshot save
[BACKUP FILE NAME]
In exam, cluster setup is done with kubeadm , this means ETCD
used by the kubernetes cluster is coming from static pod.
kubectl get pod -n kube-system
kubectl describe pod etcd-master -n kube-system
You can locate the information on
endpoint: – advertise-client-urls=https://172.17.0.15:2379
ca certificate: – trusted-cafile=/etc/kubernetes/pki/etcd/ca.crt
server certificate : – certfile=/etc/kubernetes/pki/etcd/server.crt
key: – key-file=/etc/kubernetes/pki/etcd/server.key
To Create backup
export ETCDCTL_API=3
(or)
ETCDCTL_API=3 etcdctl ETCDCTL_API=3 etcdctl —
endpoints=https://172.17.0.15:2379 —
cacert=/etc/kubernetes/pki/etcd/ca.crt —
cert=/etc/kubernetes/pki/etcd/server.crt —
key=/etc/kubernetes/pki/etcd/server.key snapshot save etcdsnapshot.db
//Verify
ETCDCTL_API=3 etcdctl –write-out=table snapshot status
snapshot.db

ETCDCTL_API=3 etcdctl –endpoints=[ENDPOINT] –cacert=[CA CERT]
–cert=[ETCD SERVER CERT] –key=[ETCD SERVER KEY] snapshot save
[BACKUP FILE NAME]
In exam, cluster setup is done with kubeadm , this means ETCD
used by the kubernetes cluster is coming from static pod.
kubectl get pod -n kube-system
kubectl describe pod etcd-master -n kube-system
You can locate the information on
endpoint: – advertise-client-urls=https://172.16.0.18:2379
ca certificate: – trusted-cafile=/etc/kubernetes/pki/etcd/ca.crt
server certificate : – certfile=/etc/kubernetes/pki/etcd/server.crt
key: – key-file=/etc/kubernetes/pki/etcd/server.key
To Create backup
export ETCDCTL_API=3
(or)
ETCDCTL_API=3 etcdctl ETCDCTL_API=3 etcdctl —
endpoints=https://172.17.0.15:2379 —
key=/etc/kubernetes/pki/etcd/server.key snapshot save etcdsnapshot.db
//Verify
ETCDCTL_API=3 etcdctl –write-out=table snapshot status
snapshot.db

QUESTION 63
Remove taint added to node “worker-2”

QUESTION 64
Create a Cronjob with busybox image that prints date and hello from kubernetes cluster message for every minute

CronJob Syntax:
* –> Minute
* –> Hours
* –> Day of The Month
* –> Month
* –> Day of the Week
*/1 * * * * –> Execute a command every one minutes.
vim date-job.yaml
apiVersion: batch/v1beta1
kind: CronJob
metadata:
name: date-job
spec:
schedule: “*/1 * * * *”
jobTemplate:
spec:
template:
spec:
containers:
– name: hello
image: busybox
args:
– /bin/sh
– -c
– date; echo Hello from the Kubernetes cluster
restartPolicy: OnFailure
kubectl apply -f date-job.yaml
//Verify
kubectl get cj date-job -o yaml

CronJob Syntax:
* –> Minute
* –> Hours
* –> Day of The Month
* –> Month
* –> Day of the Week
*/1 * * * * –> Execute a command every one minutes.
vim date-job.yaml
apiVersion: batch/v1beta1
kind: CronJob
metadata:
name: date-job
spec:
schedule: “*/1 * * * *”
jobTemplate:
spec:
template:
– /bin/sh
– -c
– date; echo Hello from the Kubernetes cluster
restartPolicy: OnFailure
kubectl apply -f date-job.yaml
//Verify
kubectl get cj date-job -o yaml

QUESTION 65
Create a persistent volume with name app-data, of capacity 2Gi and access mode ReadWriteMany. The type of volume is hostPath and its location is /srv/app-data.

QUESTION 66
Your Kubernetes cluster is experiencing a high number of pod restarts in the ‘database-service’ Deployment. The logs show errors related to “connection refused” from the database service. You need to diagnose the issue and resolve it.

QUESTION 67
Change the Image version back to 1.17.1 for the pod you just updated and observe the changes

QUESTION 68
Create a deployment as follows:
Name: nginx-app
Using container nginx with version 1.11.10-alpine
The deployment should contain
Next, deploy the application with new version , by performing a rolling update.
Finally, rollback that update to the previous version