CKA 2 - DevOpsEngine

CKA 2

1 / 10

Question

Perform the following tasks:

Create a Kubernetes secret named super-secret with the key password and value bob.
Create a pod named pod-secrets-via-file using the redis image, which mounts the secret at /secrets.
Create a second pod named pod-secrets-via-env using the redis image, which exposes the secret via an environment variable named CONFIDENTIAL.

Which configuration correctly implements the required setup?

 A.
 kubectl create secret generic super-secret --from-literal=password=bob
 ---
 apiVersion: v1
 kind: Pod
 metadata:
   name: pod-secrets-via-file
 spec:
   containers:
   - name: redis
     image: redis
     volumeMounts:
     - name: secret-vol
       mountPath: /secrets
   volumes:
   - name: secret-vol
     secret:
       secretName: super-secret

 B.
 kubectl create secret generic super-secret --from-literal=password=bob
 ---
 apiVersion: v1
 kind: Pod
 metadata:
   name: pod-secrets-via-env
 spec:
   containers:
   - name: redis
     image: redis
     env:
     - name: CONFIDENTIAL
       valueFrom:
         secretKeyRef:
           name: super-secret
           key: password

 C.
 kubectl create secret generic super-secret --from-literal=password=bob
 ---
 apiVersion: v1
 kind: Pod
 metadata:
   name: pod-secrets-via-file
 spec:
   containers:
   - name: redis
     image: redis
     envFrom:
     - secretRef:
       name: super-secret

 D.
 kubectl create secret generic super-secret --from-literal=password=bob
 ---
 apiVersion: v1
 kind: Pod
 metadata:
   name: pod-secrets-via-env
 spec:
   containers:
   - name: redis
     image: redis
     env:
     - name: password
       value: bob

2 / 10

Question

Perform the following tasks:

Add an init container to the pod named hungry-bear, defined in the spec file at /opt/KUCC00108/pod-spec-KUCC00108.yaml
The init container should create an empty file at /workdir/calm.txt
If /workdir/calm.txt is not present, the pod should exit
Once updated, create the pod using this spec file

Which of the following correctly modifies the YAML to meet all requirements?

 A.
 initContainers:
 - name: init-calm
   image: busybox
   command: ['sh', '-c', 'touch /workdir/calm.txt']
 containers:
 - name: hungry-bear
   image: nginx
   volumeMounts:
   - mountPath: /workdir
     name: calm-volume
 volumes:
 - name: calm-volume
   emptyDir: {}

 B.
 initContainers:
 - name: calm-init
   image: busybox
   command: ['sh', '-c', 'echo calm > /tmp/calm.txt']
 containers:
 - name: hungry-bear
   image: nginx

 C.
 initContainers:
 - name: init-calm
   image: alpine
   command: ['sh', '-c', 'touch /workdir/calm.txt']
 containers:
 - name: hungry-bear
   image: nginx
   volumeMounts:
   - mountPath: /workdir
     name: calm-vol
 volumes:
 - name: calm-vol
   emptyDir: {}

 D.
 initContainers:
 - name: file-checker
   image: busybox
   command: ['sh', '-c', 'exit 1']
 containers:
 - name: hungry-bear
   image: nginx

3 / 10

Question

You are required to schedule a Pod with the following characteristics:

Pod Name: kucc1
Number of App Containers: 2
Container Name/Image pairs:
- nginx (image: nginx)
- consul (image: consul)

Which of the following configurations will correctly create this pod?

 A.
 apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: kucc1
 spec:
   replicas: 1
   template:
     metadata:
       labels:
         app: kucc1
     spec:
       containers:
       - name: nginx
         image: nginx

 B.
 apiVersion: v1
 kind: Pod
 metadata:
   name: kucc1
 spec:
   containers:
   - name: nginx-container
     image: nginx
   - name: consul-container
     image: consul

 C.
 apiVersion: v1
 kind: Pod
 metadata:
   name: kucc1
 spec:
   containers:
   - name: nginx
     image: nginx
   - name: kucc1
     image: consul

 D.
 apiVersion: v1
 kind: Pod
 metadata:
   name: kucc1
 spec:
   containers:
   - name: nginx
     image: nginx
   - name: consul
     image: consul

4 / 10

Question

You are given access to a broken single-node Kubernetes cluster on host Cka000059, which was migrated from another machine.

The original cluster used an external etcd server.
After the migration, some cluster components are broken.
Your task is to identify the misconfiguration and fix all broken components so the cluster can run successfully again.

What is the correct sequence of actions to fix the issue?

 A.
 ssh Cka000059
 sudo -i
 Inspect /etc/kubernetes/manifests/kube-apiserver.yaml
 Check and fix etcd server URL to point to the external etcd
 Restart kubelet if needed
 Check cluster status with kubectl get nodes

 B.
 ssh Cka000059
 sudo -i
 Reinitialize the cluster with kubeadm init
 Deploy a new etcd server as a pod
 Edit all manifests in /etc/kubernetes/manifests to use the new etcd
 Check cluster status

 C.
 ssh Cka000059
 sudo -i
 Edit /etc/kubernetes/kubelet.conf
 Replace the kubeconfig cluster server entry
 Restart the kubelet
 Run kubectl get pods

 D.
 ssh Cka000059
 sudo -i
 Delete the kube-apiserver.yaml manifest
 Recreate it using kubeadm init phase commands
 Restart kubelet
 Check if etcd is running locally and connect to it

5 / 10

Question

Configure the kubelet systemd-managed service on the node labeled with name=wk8s-node-1 so that it automatically launches a pod containing:

A single container
Image: httpd
Container name: webtool

🔧 Place the required pod spec file in the following directory: /etc/kubernetes/manifests

💡 You can SSH and elevate privileges using:
– ssh wk8s-node-1
– sudo -i

 A.
 ssh wk8s-node-1
 sudo -i
 cat > /etc/kubernetes/manifests/webtool.yaml <<EOF
 apiVersion: v1
 kind: Pod
 metadata:
   name: webtool
 spec:
   containers:
   - name: webtool
     image: httpd
 EOF

 B.
 ssh wk8s-node-1
 sudo -i
 cat > /etc/kubernetes/manifests/webtool.yaml <<EOF
 apiVersion: v1
 kind: Deployment
 metadata:
   name: webtool
 spec:
   replicas: 1
   template:
     metadata:
       labels:
         app: webtool
     spec:
       containers:
       - name: webtool
         image: httpd
 EOF

 C.
 ssh wk8s-node-1
 sudo -i
 cat > /etc/kubernetes/manifests/webtool.yaml <<EOF
 apiVersion: v1
 kind: Pod
 metadata:
   name: httpd
 spec:
   containers:
   - name: webtool
     image: httpd
 EOF

 D.
 ssh wk8s-node-1
 sudo -i
 cat > /etc/kubernetes/manifests/webtool.yaml <<EOF
 apiVersion: v1
 kind: Pod
 metadata:
   name: webtool
 spec:
   containers:
   - name: webtool
     image: nginx
 EOF

6 / 10

Question

You are required to list all pods, sorted by their creation timestamp (from oldest to newest).
Which of the following commands achieves this correctly?

 A.
 kubectl get pods --all-namespaces --sort-by=.metadata.creationTimestamp

 B.
 kubectl get pods --sort-by=.status.startTime

 C.
 kubectl get pods --sort-by='.metadata.creationTimestamp'

 D.
 kubectl get pods -A --sort-by='{.metadata.creationTimestamp}'

7 / 10

Question

Create a PersistentVolume with the following specifications:

Name: app-data
Capacity: 1Gi
Access Mode: ReadOnlyMany
Type: hostPath
Path: /srv/app-data

Which of the following YAML definitions is correct?

 A.
 apiVersion: v1
 kind: PersistentVolume
 metadata:
   name: app-data
 spec:
   capacity:
     storage: 1Gi
   accessModes:
     - ReadOnlyMany
   hostPath:
     path: /srv/app-data

 B.
 apiVersion: v1
 kind: PersistentVolume
 metadata:
   name: app-data
 spec:
   capacity:
     storage: 1Gi
   accessModes:
     - ReadOnlyMany
   volumeMode: Filesystem
   hostPath:
     path: /srv/app-data

 C.
 apiVersion: v1
 kind: PersistentVolume
 metadata:
   name: app-data
 spec:
   accessModes:
     - ReadOnlyMany
   capacity:
     storage: 1Gi
   nfs:
     path: /srv/app-data

 D.
 apiVersion: v1
 kind: PersistentVolume
 metadata:
   name: app-data
 spec:
   capacity:
     storage: 1Gi
   accessModes:
     - ReadWriteOnce
   hostPath:
     path: /srv/app-data

8 / 10

Question

List all pods across all namespaces, showing only the pod name and namespace, using a JSONPath expression.

 A.
 kubectl get pods -A -o=jsonpath='{.items[*].metadata.name} {.items[*].metadata.namespace}'

 B.
 kubectl get pods --all-namespaces -o=jsonpath='{range .items[*]}{.metadata.name}{"t"}{.metadata.namespace}{"n"}{end}'

 C.
 kubectl get pods --all-namespaces -o custom-columns=NAME:.metadata.name,NAMESPACE:.metadata.namespace

 D.
 kubectl get pods -n kube-system -o=jsonpath='{range .items[*]}{.metadata.name}{" "}{.metadata.namespace}{"n"}{end}'

9 / 10

Check how many worker nodes are in the Ready state, excluding nodes tainted with NoSchedule, and write the count to the file: /opt/KUCC00104/kucc00104.txt

 A.
 kubectl get nodes --no-headers | grep -v 'NoSchedule' | grep ' Ready' | wc -l > /opt/KUCC00104/kucc00104.txt

 B.
 kubectl get nodes -o json | jq '[.items[] | select(.spec.taints == null or all(.spec.taints[]; .effect != "NoSchedule")) | select(.status.conditions[] | select(.type=="Ready" and .status=="True"))] | length' > /opt/KUCC00104/kucc00104.txt

 C.
 kubectl describe nodes | grep -v NoSchedule | grep Ready | wc -l > /opt/KUCC00104/kucc00104.txt

 D.
 kubectl get nodes -o jsonpath='{range .items[?(@.spec.taints[0].effect!="NoSchedule")]}{.status.conditions[?(@.type=="Ready")].status}{"n"}{end}' | grep True | wc -l > /opt/KUCC00104/kucc00104.txt

10 / 10

Create a deployment with the following specifications:

Name: nginx-app
Image: nginx:1.11.10-alpine
Replicas: 3

Then:

Perform a rolling update to version 1.11.13-alpine.
Rollback the deployment to version 1.11.10-alpine.

Which of the following command sets will correctly complete this task?

 A.
 kubectl create deployment nginx-app --image=nginx:1.11.10-alpine --replicas=3
 kubectl set image deployment/nginx-app nginx=nginx:1.11.13-alpine
 kubectl rollout undo deployment/nginx-app

 B.
 kubectl run nginx-app --image=nginx:1.11.10-alpine --replicas=3
 kubectl set image deployment/nginx-app nginx=nginx:1.11.13-alpine
 kubectl rollout undo deployment/nginx-app

 C.
 kubectl create deployment nginx-app --image=nginx:1.11.13-alpine --replicas=3
 kubectl set image deployment/nginx-app nginx=nginx:1.11.10-alpine
 kubectl rollout undo deployment/nginx-app

 D.
 kubectl create deployment nginx-app --image=nginx:1.11.10-alpine --replicas=3
 kubectl set image deployment/nginx-app nginx=nginx:1.11.13-alpine
 kubectl delete deployment nginx-app && kubectl create deployment nginx-app --image=nginx:1.11.10-alpine --replicas=3

Your score is

Question

✔️ Correct Answer: B

🔍 Explanation

✔️ Correct Answer: B

🔍 Explanation

Question

✔️ Correct Answer: C

🔍 Explanation

✔️ Correct Answer: C

🔍 Explanation

Question

✔️ Correct Answer: D

🔍 Explanation

✔️ Correct Answer: D

🔍 Explanation

Question

✔️ Correct Answer: A

🔍 Explanation

✔️ Correct Answer: A

🔍 Explanation

Question

✔️ Correct Answer: A

🔍 Explanation

✔️ Correct Answer: A

🔍 Explanation

Question

✔️ Correct Answer: A

🔍 Explanation

✔️ Correct Answer: A

🔍 Explanation

Question

✔️ Correct Answer: B

🔍 Explanation

✔️ Correct Answer: B

🔍 Explanation

Question

✔️ Correct Answer: B

🔍 Explanation

✔️ Correct Answer: B

🔍 Explanation

✔️ Correct Answer: D

🔍 Explanation

✔️ Correct Answer: D

🔍 Explanation

✔️ Correct Answer: A

🔍 Explanation

✔️ Correct Answer: A

🔍 Explanation