Linux Foundation CKAD dumps - 100% Pass Guarantee!

CORRECT TEXT

Context

You have been tasked with scaling an existing deployment for availability, and creating a service to expose the deployment within your infrastructure.

Task

Start with the deployment named kdsn00101-deployment which has already been deployed to the namespace kdsn00101. Edit it to:

1.

Add the func=webFrontEnd key/value label to the pod template metadata to identify the pod for the service definition

2.

Have 4 replicas

Next, create and deploy in namespace kdsn00l01 a service that accomplishes the following:

1.

Exposes the service on TCP port 8080

2.

is mapped to me pods defined by the specification of kdsn00l01-deployment

3.

Is of type NodePort

4.

Has a name of cherry

A. Please check explanations

B. Place Holder

CORRECT TEXT

Context

A user has reported an application is unreachable due to a failing livenessProbe .

Task

Perform the following tasks:

Find the broken pod and store its name and namespace to /opt/KDOB00401/broken.txt in the format:

The output file has already been created

1.

Store the associated error events to a file /opt/KDOB00401/error.txt, The output file has already been created. You will need to use the -o wide output specifier with your command

2.

Fix the issue.

A. Please check explanations

B. Place Holder

CORRECT TEXT

Context

A container within the poller pod is hard-coded to connect the nginxsvc service on port 90 . As this port changes to 5050 an additional container needs to be added to the poller pod which adapts the container to connect to this new port. This should be realized as an ambassador container within the pod.

Task

Update the nginxsvc service to serve on port 5050. Add an HAproxy container named haproxy bound to port 90 to the poller pod and deploy the enhanced pod. Use the image haproxy and inject the configuration located at /opt/KDMC00101/haproxy.cfg, with a ConfigMap named haproxyconfig, mounted into the container so that haproxy.cfg is available at /usr/local/etc/haproxy/haproxy.cfg. Ensure that you update the args of the poller container to connect to localhost instead of nginxsvc so that the connection is correctly proxied to the new service endpoint. You must not modify the port of the endpoint in poller's args . The spec file used to create the initial poller pod is available in /opt/KDMC00101/poller.yaml

A. Please check explanations

B. Place Holder

CORRECT TEXT

Task:

Create a Pod named nginx resources in the existing pod resources namespace.

Specify a single container using nginx:stable image.

Specify a resource request of 300m cpus and 1Gi of memory for the Pod's container.

A. Please check explanations

B. Place Holder

CORRECT TEXT

Context

Developers occasionally need to submit pods that run periodically.

Task

Follow the steps below to create a pod that will start at a predetermined time and]which runs to completion only once each time it is started:

Create a YAML formatted Kubernetes manifest /opt/KDPD00301/periodic.yaml that runs the following shell command: date in a single busybox container.

The command should run every minute and must complete within 22 seconds or be terminated oy Kubernetes. The Cronjob name and container name should both be hello

Create the resource in the above manifest and verify that the job executes successfully at least once

A. Please check explanations

B. Place Holder