Home / Linux Foundation / CKA

Question list

List of questions

Question 1

(0)

Monitor the logs of pod foo and: Extract log lines corresponding to error unable-to-access-website Write them to /opt/KULM00201/foo

Question 2

(0)

List all persistent volumes sorted by capacity, saving the full kubectl output to /opt/KUCC00102/volume_list. Use kubectl 's own functionality for sorting the output, and do not manipulate it any fu

Question 3

(0)

Ensure a single instance of pod nginx is running on each node of the Kubernetes cluster where nginx also represents the Image name which has to be used. Do not override any taints currently in place

Question 4

(0)

Perform the following tasks: Add an init container to hungry-bear (which has been defined in spec file /opt/KUCC00108/pod-spec-KUCC00108.yaml ) The init container should create an empty file name

Question 5

(0)

Create a pod named kucc8 with a single app container for each of the following images running inside (there may be between 1 and 4 images specified): nginx + redis + memcached.

Question 6

(0)

Schedule a pod as follows: Name: nginx-kusc00101 Image: nginx Node selector: disk=ssd

Question 7

(0)

Create a deployment as follows: Name: nginx-app Using container nginx with version 1.11.10-alpine The deployment should contain 3 replicas Next, deploy the application with new version 1.11.13-a

Question 8

(0)

Create and configure the service front-end-service so it's accessible through NodePort and routes to the existing pod named front-end.

Question 9

(0)

Create a pod as follows: Name: mongo Using Image: mongo In a new Kubernetes namespace named: my-website

Question 10

(0)

Create a deployment spec file that will: Launch 7 replicas of the nginx Image with the label app_runtime_stage=dev deployment name: kual00201 Save a copy of this spec file to /opt/KUAL00201/spec_d

Question 54 - CKA discussion

Score: 7%

Task

Reconfigure the existing deployment front-end and add a port specification named http exposing port 80/tcp of the existing container nginx.

Create a new service named front-end-svc exposing the container port http.

Configure the new service to also expose the individual Pods via a NodePort on the nodes on which they are scheduled.

See the solution below.

Show Answer

asked 18/09/2024

Ahmed Dawoud

41 questions

Your answer: A

0 comments

Sorted by