Certified Kubernetes Administrator (CKA) Dumps Questions Updated (V9.02) With Correct Answers

1. CORRECT TEXT

Perform the following tasks:

✑ Add an init container to hungry-bear (which has been defined in spec file /opt/KUCC00108/pod-spec-KUCC00108.yaml)

✑ The init container should create an empty file named/workdir/calm.txt

✑ If /workdir/calm.txt is not detected, the pod should exit

✑ Once the spec file has been updated with the init container definition, the pod should be created

2. CORRECT TEXT

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.

3. CORRECT TEXT

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

4. CORRECT TEXT

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

5. CORRECT TEXT

Score: 7%

Task

Create a new nginx Ingress resource as follows:

• Name: ping

• Namespace: ing-internal

• Exposing service hi on path /hi using service port 5678

6. CORRECT TEXT

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 Ci

7. CORRECT TEXT

Ensure a single instance of pod nginx is running on each node of the Kubernetes cluster where nginx also represents the Image name which has to be used. Do not

override any taints currently in place.

Use DaemonSet to complete this task and use ds-kusc00201 as DaemonSet name.

8. CORRECT TEXT

Create and configure the service front-end-service so it's accessiblethrough NodePort and routes to the existing pod named front-end.

9. CORRECT TEXT

Scale the deployment webserver to 6 pods.

10. CORRECT TEXT

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

11. CORRECT TEXT

Score: 4%

Context

You have been asked to create a new ClusterRole for a deployment pipeline and bind it to a specific ServiceAccount scoped to a specific namespace.

Task

Create a new ClusterRole named deployment-clusterrole, which only allows to create the following resource types:

• Deployment

• StatefulSet

• DaemonSet

Create a new ServiceAccount named cicd-token in the existing namespace app-team1.

Bind the new ClusterRole deployment-clusterrole lo the new ServiceAccount cicd-token, limited to the namespace app-team1.

12. CORRECT TEXT

Score: 5%

Task

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/KUTR00401/KUTR00401.txt (which already exists).

13. CORRECT TEXT

Score: 4%

Task

Schedule a pod as follows:

• Name: nginx-kusc00401

• Image: nginx

• Node selector: disk=ssd

14. CORRECT TEXT

Score: 7%

Task

Given an existing Kubernetes cluster running version 1.20.0, upgrade all of the Kubernetes control plane and node components on the master node only to version 1.20.1.

Be sure to drain the master node before upgrading it and uncordon it after the upgrade.

You are also expected to upgrade kubelet and kubectl on the master node.

15. CORRECT TEXT

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.

16. CORRECT TEXT

Create an nginx pod and list the pod with different levels of verbosity

17. CORRECT TEXT

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

18. CORRECT TEXT

Score:7%

Task

Create a new PersistentVolumeClaim

• Name: pv-volume

• Class: csi-hostpath-sc

• Capacity: 10Mi

Create a new Pod which mounts the PersistentVolumeClaim as a volume:

• Name: web-server

• Image: nginx

• Mount path: /usr/share/nginx/html

Configure the new Pod to have ReadWriteOnce access on the volume.

Finally, using kubectl edit or kubectl patch expand the PersistentVolumeClaim to a capacity of 70Mi and record that change.

19. CORRECT TEXT

Create a file:

/opt/KUCC00302/kucc00302.txt that lists all pods that implement service baz in namespace development.

The format of the file should be one pod name per line.

20. CORRECT TEXT

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 namespace and the volume must not be persistent.