Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Free Linux Foundation CKA Exam Dumps

Here you can find all the free questions related with Linux Foundation Certified Kubernetes Administrator (CKA) exam. You can also find on this page links to recently updated premium files with which you can practice for actual Linux Foundation Certified Kubernetes Administrator Exam. These premium versions are provided as CKA exam practice tests, both as desktop software and browser based application, you can use whatever suits your style. Feel free to try the Certified Kubernetes Administrator Exam premium files for free, Good luck with your Linux Foundation Certified Kubernetes Administrator Exam.
Question No: 11

MultipleChoice

SIMULATION

Given a partially-functioning Kubernetes cluster, identify symptoms of failure on the cluster.

Determine the node, the failing service, and take actions to bring up the failed service and restore the health of the cluster. Ensure that any changes are made permanently.

You can ssh to the relevant I nodes (bk8s-master-0 or bk8s-node-0) using:

[student@node-1] $ ssh <nodename>

You can assume elevated privileges on any node in the cluster with the following command:

[student@nodename] $ | sudo --i

Options
Question No: 12

MultipleChoice

SIMULATION

Configure the kubelet systemd- managed service, on the node labelled with name=wk8s-node-1, to launch a pod containing a single container of Image httpd named webtool automatically. Any spec files required should be placed in the /etc/kubernetes/manifests directory on the node.

You can ssh to the appropriate node using:

[student@node-1] $ ssh wk8s-node-1

You can assume elevated privileges on the node with the following command:

[student@wk8s-node-1] $ | sudo --i

Options
Question No: 13

MultipleChoice

SIMULATION

Scale the deployment webserver to 6 pods.

Options
Question No: 14

MultipleChoice

SIMULATION

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

solution

Options
Question No: 15

MultipleChoice

SIMULATION

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.

Options
Question No: 16

MultipleChoice

SIMULATION

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

Options
Question No: 17

MultipleChoice

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

Options
Question No: 18

MultipleChoice

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.

Options
Question No: 19

MultipleChoice

Score: 7%

Task

Next, restore an existing, previous snapshot located at /var/lib/backup/etcd-snapshot-previo us.db

Options
Question No: 20

MultipleChoice

SIMULATION

Create a pod as follows:

* Name: mongo

* Using Image: mongo

* In a new Kubernetes namespace named: my-website

Options

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77