Kubernetes Administrator Certified Official Practice Test CKA – Aug-2024 [Q27-Q49]

admin -

August 5, 2024

4/5 - (1 vote)

Kubernetes Administrator Certified Official Practice Test CKA – Aug-2024

Ace Linux Foundation CKA Certification with Actual Questions Aug 05, 2024 Updated

The CKA exam is a hands-on, performance-based exam that requires candidates to demonstrate their knowledge of Kubernetes administration through the use of practical tasks and challenges. CKA exam is designed to test an individual’s ability to configure and manage Kubernetes clusters, troubleshoot common issues, and deploy applications using Kubernetes. CKA exam is administered online and can be taken from anywhere in the world.

The CKA exam is designed to test the knowledge and proficiency of professionals in Kubernetes administration. CKA exam consists of a set of performance-based tasks that assess the candidate’s ability to deploy, configure, manage, and troubleshoot Kubernetes clusters. CKA exam is conducted online and requires candidates to complete a set of practical tasks within a specified time frame. CKA exam covers a wide range of Kubernetes administration topics, including cluster architecture, networking, storage, security, and troubleshooting.

QUESTION 27
Pause the rollout of the deployment

kubectl rollout pause deploy webapp

QUESTION 28
Configure the kubelet systemd- managed service, on the node labelled with name=wk8s-node-1, to launch a pod containing a single container of Image httpd named webtool automatically. Any spec files required should be placed in the /etc/kubernetes/manifests directory on the node.
You can ssh to the appropriate node using:
[student@node-1] $ ssh wk8s-node-1
You can assume elevated privileges on the node with the following command:
[student@wk8s-node-1] $ | sudo -i

solution

QUESTION 29
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.

See the solution below.
Explanation
Solution:

QUESTION 30
Create a configmap called cfgvolume with values var1=val1,
var2=val2 and create an nginx pod with volume nginx-volume which
reads data from this configmap cfgvolume and put it on the path
/etc/cfg

// first create a configmap cfgvolume
kubectl create cm cfgvolume –from-literal=var1=val1 –fromliteral=var2=val2
// verify the configmap
kubectl describe cm cfgvolume
// create the config map
kubectl create -f nginx-volume.yml
vim nginx-configmap-pod.yaml
apiVersion: v1
kind: Pod
– name: nginx-volume
configMap:
name: cfgvolume
containers:
– image: nginx
name: nginx
volumeMounts:
– name: nginx-volume
mountPath: /etc/cfg
restartPolicy: Always
k kubectl apply -f nginx-configmap-pod.yaml
/ // Verify
// exec into the pod
kubectl exec -it nginx — /bin/sh
// check the path
cd /etc/cfg

// first create a configmap cfgvolume
kubectl create cm cfgvolume –from-literal=var1=val1 –fromliteral=var2=val2
// verify the configmap
kubectl describe cm cfgvolume
// create the config map
kubectl create -f nginx-volume.yml
vim nginx-configmap-pod.yaml
apiVersion: v1
kind: Pod
metadata:
labels:
run: nginx
name: nginx
spec:
volumes:
– name: nginx-volume
configMap:
name: cfgvolume
containers:
– image: nginx
name: nginx
volumeMounts:
– name: nginx-volume
mountPath: /etc/cfg
restartPolicy: Always
k kubectl apply -f nginx-configmap-pod.yaml
/ // Verify
// exec into the pod
kubectl exec -it nginx — /bin/sh
// check the path
cd /etc/cfg

QUESTION 31
Change the label for one of the pod to env=uat and list all the pods to verify

kubectl label pod/nginx-dev3 env=uat –overwrite kubectl get pods –show-labels

QUESTION 32
For this item, you will have to ssh and complete all tasks on these
nodes. Ensure that you return to the base node (hostname: ) when you have completed this item.
Context
As an administrator of a small development team, you have been asked to set up a Kubernetes cluster to test the viability of a new application.
Task
You must use kubeadm to perform this task. Any kubeadm invocations will require the use of the
–ignore-preflight-errors=all option.
Configure the node ik8s-master-O as a master node. .
Join the node ik8s-node-o to the cluster.

See the solution below.
Explanation
solution
You must use the kubeadm configuration file located at /etc/kubeadm.conf when initializingyour cluster.
You may use any CNI plugin to complete this task, but if you don’t have your favourite CNI plugin’s manifest URL at hand, Calico is one popular option:
https://docs.projectcalico.org/v3.14/manifests/calico.yaml
Docker is already installed on both nodes and apt has been configured so that you can install the required tools.

QUESTION 33
Create a Kubernetes secret as follows:
Name: super-secret
password: bob
Create a pod named pod-secrets-via-file, using the redis Image, which mounts a secret named super-secret at
/secrets.
Create a second pod named pod-secrets-via-env, using the redis Image, which exports password as CONFIDENTIAL

See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\12 B.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\12 C.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\12 D.JPG

QUESTION 34
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.

See the solution below.
Explanation
solution

QUESTION 35
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).

kubectl delete pod test-redis kubectl create -f test-redis.yaml kubectl exec -it test-redis /bin/sh cat /data/redis/file.txt // file doesn’t exist

QUESTION 36
Get list of PVs and order by size and write to file “/opt/pvstorage.txt”

kubectl get pv –sort-by=.spec.capacity.storage > /opt/pv storage.txt

QUESTION 37
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 38
On the NGFW, how can you generate and block a private key from export and thus harden your security posture and prevent rogue administrators or other bad actors from misusing keys?

1) Select Device > Certificates
2) Select Certificate Profile.
3) Generate the certificate
4) Select Block Private Key Export.

1) Select Device > Certificate Management > Certificates >Device > Certificates
2) Import the certificate.
3) Select Import Private Key
4) Click Generate to generate the new certificate.

1) Select Device > Certificates
2) Select Certificate Profile
3) Generate the certificate
4) Select Block Private Key Export

1) Select Device > Certificate Management > Certificates Device > Certificates
2) Generate the certificate.
3) Select Block Private Key Export.
4) Click Generate to generate the new certificate.

QUESTION 39
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 thestagingnamespace and the volumemust notbe persistent.

See the solution below.
Explanation
solution

QUESTION 40
Create a pod as follows:
Name: mongo
Using Image: mongo
In a new Kubernetes namespace named: my-website

solution

QUESTION 41
Create a redis pod, and have it use a non-persistent storage
Note: In exam, you will have access to kubernetes.io site,
Refer : https://kubernetes.io/docs/tasks/configure-pod-container/configurevolume-storage/

apiVersion: v1
kind: Pod
metadata:
name: redis
spec:
containers:
– name: redis
image: redis
volumeMounts:
– name: redis-storage
mountPath: /data/redis
ports:
– containerPort: 6379
volumes:
– name: redis-storage
emptyDir: {}

apiVersion: v1
kind: Pod
metadata:
name: redis
spec:
containers:
– name: redis
image: redis
volumeMounts:
– containerPort: 6379
volumes:
– name: redis-storage
emptyDir: {}

QUESTION 42
Scale the deploymentwebserverto6pods.

See the solution below.
Explanation
solution

QUESTION 43
Clean the cluster by deleting deployment and hpa you just created

kubectl delete deploy webapp kubectl delete hpa webapp

QUESTION 44
List all configmap and secrets in the cluster in all namespace and write it to a file /opt/configmap-secret

kubectl get configmap,secrets –all-namespaces > /opt/configmap-secret // Verify Cat /opt/configmap-secret

QUESTION 45
Create a redis pod named “test-redis” and exec into that pod and create a file named “test-file.txt” with the text ‘This is called the test file’ in the path /data/redis and open another tab and exec again with the same pod and verifies file exist in the same path.

vim test-redis.yaml
apiVersion: v1
kind: Pod
metadata:
name: test-redis
spec:
containers:
– name: redis
image: redis
ports:
– containerPort: 6379
volumeMounts:
– mountPath: /data/redis
name: redis-storage
volumes:
– name: redis-storage
emptyDir: {}
kubectl apply -f redis-pod-vol.yaml
// first terminal
kubectl exec -it test-redis /bin/sh
cd /data/redis
echo ‘This is called the test file’ > file.txt
//open another tab
kubectl exec -it test-redis /bin/sh
cat /data/redis/file.txt

vim test-redis.yaml
apiVersion: v1
kind: Pod
metadata:
name: test-redis
spec:
containers:
– name: redis
image: redis
ports:
– containerPort: 6379
volumeMounts:
– mountPath: /data/redis
name: redis-storage
volumes:
kubectl exec -it test-redis /bin/sh
cd /data/redis
echo ‘This is called the test file’ > file.txt
//open another tab
kubectl exec -it test-redis /bin/sh
cat /data/redis/file.txt

QUESTION 46
Evict all existing pods from a node-1 and make the node unschedulable for new pods.

kubectl get nodes
kubectl drain node-1 #It will evict pods running on node-1 to
other nodes in the cluster
kubectl cordon node-1 # New pods cannot be scheduled to the
node
// Verify
kubectl get no
When you cordon a node, the status shows “SchedulingDisabled”

kubectl get nodes
kubectl drain node-1 #It will evict pods running on node-1 to
other nodes in the cluster
// Verify
kubectl get no
When you cordon a node, the status shows “SchedulingDisabled”

QUESTION 47
Print pod name and start time to “/opt/pod-status” file

kubect1 get pods -o=jsonpath='{range .items[*]}{.metadata.name}{“\t”}{.status.podIP}{“\n”}{end}’

QUESTION 48
Create a namespace called ‘development’ and a pod with image nginx called nginx on this namespace.

kubectl create namespace development
kubectl run nginx –image=nginx –restart=Never -n development

QUESTION 49
Configure the kubelet systemd- managed service, on the node labelled with name=wk8s-node-1, to launch a pod containing a single container of Image httpd named webtool automatically. Any spec files required should be placed in the /etc/kubernetes/manifests directory on the node.
You can ssh to the appropriate node using:
[student@node-1] $ ssh wk8s-node-1
You can assume elevated privileges on the node with the following command:
[student@wk8s-node-1] $ | sudo -i

See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\21 C.JPG