Question 1

Exhibit:
Context
You are asked to prepare a Canary deployment for testing a new application release.
Task:
A Service named krill-Service in the goshark namespace points to 5 pod created by the Deployment named current-krill-deployment

Accepted Answer

Solution:
Text Description automatically generated

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)

Question 2

Exhibit:
Task:
Key3: value1
Add an environment variable named BEST_VARIABLE consuming the value of the secret key3.

Accepted Answer

Solution:
Text Description automatically generated

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)
Text Description automatically generated

Question 3

Exhibit:
Task:
Create a Deployment named expose in the existing ckad00014 namespace running 6 replicas of a Pod. Specify a single container using the ifccncf/nginx: 1.13.7
image
Add an environment variable named NGINX_PORT with the value 8001 to the container then expose port 8001

Accepted Answer

Solution:

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)
Text Description automatically generated
Text Description automatically generated

Question 4

Exhibit:

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)
Context
A web application requires a specific version of redis to be used as a cache. Task
Create a pod with the following characteristics, and leave it running when complete:
• The pod must run in the web namespace. The namespace has already been created
• The name of the pod should be cache
• Use the Ifccncf/redis image with the 3.2 tag
• Expose port 6379

Accepted Answer

Solution:

Question 5

Exhibit:
Task:
1- Update the Propertunel scaling configuration of the Deployment web1 in the ckad00015 namespace setting maxSurge to 2 and maxUnavailable to 59
2- Update the web1 Deployment to use version tag 1.13.7 for the Ifconf/nginx container image. 3- Perform a rollback of the web1 Deployment to its previous
version

Accepted Answer

Solution:
Text Description automatically generated

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)

Question 6

Exhibit:
Task:
 To run 2 replicas of the pod
 Add the following label on the pod:
Role userUI

Accepted Answer

Solution:
Text Description automatically generated
Text Description automatically generated
Text Description automatically generated

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)

Question 7

Exhibit:
Task:
A Dockerfile has been prepared at -/human-stork/build/Dockerfile

Accepted Answer

Solution:

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)

Question 8

Exhibit:
Context
A pod is running on the cluster but it is not responding. Task
The desired behavior is to have Kubemetes restart the pod when an endpoint returns an HTTP 500 on the
/healthz endpoint. The service, probe-pod, should never send traffic to the pod while it is failing. Please complete the following:
• The application has an endpoint, /started, that will indicate if it can accept traffic by returning an HTTP 200. If the endpoint returns an HTTP 500, the application
has not yet finished initialization.
• The application has another endpoint /healthz that will indicate if the application is still working as expected by returning an HTTP 200. If the endpoint returns an
HTTP 500 the application is no longer responsive.
• Configure the probe-pod pod provided to use these endpoints
• The probes should use port 8080

Accepted Answer

Solution:
apiVersion: v1 kind: Pod metadata: labels:
test: liveness
name: liveness-exec
spec: containers:
- name: liveness
image: k8s.gcr.io/busybox
args:
- /bin/sh
- -c
- touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600
livenessProbe: exec: command:
- cat
- /tmp/healthy
initialDelaySeconds: 5
periodSeconds: 5
In the configuration file, you can see that the Pod has a single Container. The periodSeconds field specifies that the kubelet should perform a liveness probe every
5 seconds. The initialDelaySeconds field tells the kubelet that it should wait 5 seconds before performing the first probe. To perform a probe, the kubelet
executes the command cat /tmp/healthy in the target container. If the command succeeds, it returns 0, and the kubelet considers the container to be alive and
healthy. If the command returns a non-zero value, the kubelet kills the container and restarts it.
When the container starts, it executes this command:
/bin/sh -c "touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600"
For the first 30 seconds of the container's life, there is a /tmp/healthy file. So during the first 30 seconds, the command cat /tmp/healthy returns a success code.
After 30 seconds, cat /tmp/healthy returns a failure co
Create the Pod:
kubectl apply -f https://k8s.io/examples/pods/probe/exec-liveness.yaml Within 30 seconds, view the Pod events:
kubectl describe pod liveness-exec
The output indicates that no liveness probes have failed yet:
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ ------
24s 24s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "k8s.gcr.io/busybox" 23s 23s 1 {kubelet worker0} spec.containers{liveness}
Normal Pulled Successfully pulled image
"k8s.gcr.io/busybox"
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
After 35 seconds, view the Pod events again: kubectl describe pod liveness-exec
At the bottom of the output, there are messages indicating that the liveness probes have failed, and the containers have been killed and recreated.
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ ------
37s 37s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "k8s.gcr.io/busybox" 36s 36s 1 {kubelet worker0} spec.containers{liveness}
Normal Pulled Successfully pulled image
"k8s.gcr.io/busybox"
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined]
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e
2s 2s 1 {kubelet worker0} spec.containers{liveness} Warning Unhealthy Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory
Wait another 30 seconds, and verify that the container has been restarted: kubectl get pod liveness-exec
The output shows that RESTARTS has been incremented: NAME READY STATUS RESTARTS AGE
liveness-exec 1/1 Running 1 1m

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)

Question 9

Exhibit:
Task:
Modify the existing Deployment named broker-deployment running in namespace quetzal so that its containers.
The broker-deployment is manifest file can be found at:

Accepted Answer

Solution:
Text Description automatically generated

Question 10

Exhibit:

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)
Given a container that writes a log file in format A and a container that converts log files from format A to format B, create a deployment that runs both containers
such that the log files from the first container are converted by the second container, emitting logs in format B.
Task:
• Create a deployment named deployment-xyz in the default namespace, that:
•Includes a primary
lfccncf/busybox:1 container, named logger-dev
•includes a sidecar Ifccncf/fluentd:v0.12 container, named adapter-zen
•Mounts a shared volume /tmp/log on both containers, which does not persist when the pod is deleted
•Instructs the logger-dev container to run the command
which should output logs to /tmp/log/input.log in plain text format, with example values:
• The adapter-zen sidecar container should read /tmp/log/input.log and output the data to /tmp/log/output.* in Fluentd JSON format. Note that no knowledge of
Fluentd is required to complete this task: all you will need to achieve this is to create the ConfigMap from the spec file provided at /opt/KDMC00102/fluentdconfigma p.yaml , and mount that ConfigMap to /fluentd/etc in the adapter-zen sidecar container

Accepted Answer

Solution:

From SurePassExam
https://www.surepassexam.com/CKAD-exam-dumps.html (33 New Questions)