linux foundation cka practice test

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

SIMULATION
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

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

SIMULATION
Scale the deployment webserver to 6 pods.

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

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

SIMULATION
Create a deployment as follows:
Name: nginx-random
Exposed via a service nginx-random
Ensure that the service and 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 and pod and write the output
to /opt/KUNW00601/service.dns and /opt/KUNW00601/pod.dns respectively.

SIMULATION
Create a snapshot of the etcd instance running at https://127.0.0.1:2379, saving the snapshot to the
file path /srv/data/etcd-snapshot.db.
The following TLS certificates/key are supplied for connecting to the server with etcdctl:
CA certificate: /opt/KUCM00302/ca.crt
Client certificate: /opt/KUCM00302/etcd-client.crt
Client key: Topt/KUCM00302/etcd-client.key

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

SIMULATION
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