Linux Foundation CKA Test Engine Dumps Training With 122 Questions [Q51-Q73]

NO.51 Your organization uses a private DNS server for internal services and requires all Kubernetes pods to resolve names against this DNS server. You need to configure CoreDNS to forward all DNS requests to this private server.

NO.52 You are deploying a microservices application on Kubernetes where each service has its own dedicated namespace. You want to implement a robust network security policy that allows communication between specific services only. How can you achieve this using NetworkPolicies?

NO.53 You need to deploy a microservice application that uses a custom DNS service for internal communication between microservices. This DNS service is not a standard Kubernetes DNS service. How would you configure Kubernetes to use your custom DNS service for the internal communication of your application?

NO.54 For this item, you will have to ssh and complete all tasks on these
nodes. Ensure that you return to the base node (hostname: ) when you have completed this item.
Context
As an administrator of a small development team, you have been asked to set up a Kubernetes cluster to test the viability of a new application.
Task
You must use kubeadm to perform this task. Any kubeadm invocations will require the use of the
–ignore-preflight-errors=all option.
Configure the node ik8s-master-O as a master node. .
Join the node ik8s-node-o to the cluster.

NO.55 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.

NO.56 List all the pods sorted by name

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

NO.58 Annotate the pod with name=webapp

NO.59 Remove taint added to node “worker-2”

NO.60 Your Kubernetes cluster is experiencing a high number of pod restarts in the ‘database-service’ Deployment. The logs show errors related to “connection refused” from the database service. You need to diagnose the issue and resolve it.

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

NO.62 You have a StatefulSet named ‘database-statefulset’ that runs a database service. The database requires persistent data storage. You are experiencing a problem where the database pods are crashing repeatedly, and the database data is getting lost. You suspect that there is an issue with the persistent volume claim (PVC) used by the StatefulSet. How would you troubleshoot and potentially fix this problem?

NO.63 You have a Kubernetes cluster with three nodes. You need to create a Role that allows users in the “developers” group to access the “nginx-deployment” deployment in the “default” namespace. This role should only permit users to view and update the deployment, not delete it.

NO.64 You have a StatefulSet named ‘mysql-cluster’ running a MySQL database with 3 replicas. You want to add a new replica to the cluster without disrupting the existing database operations. How do you achieve this while ensuring data consistency and minimal downtime?

NO.65 Scale the deployment from 5 replicas to 20 replicas and verify

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

NO.67 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.

NO.68 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.

NO.69 A Kubernetes worker node, named .Investigate why this is the case,
andperform any appropriate steps tobring the node to a state,ensuring that any changes are madepermanent.
You cansshto the failednode using:
[student@node-1] $ | sshWk8s-node-0
You can assume elevatedprivileges on the node with thefollowing command:
[student@w8ks-node-0] $ |sudo -i

NO.70 Score:7%

Context
An existing Pod needs to be integrated into the Kubernetes built-in logging architecture (e. g. kubectl logs). Adding a streaming sidecar container is a good and common way to accomplish this requirement.
Task
Add a sidecar container named sidecar, using the busybox Image, to the existing Pod big-corp-app. The new sidecar container has to run the following command:
/bin/sh -c tail -n+1 -f /va r/log/big-corp-app.log
Use a Volume, mounted at /var/log, to make the log file big-corp-app.log available to the sidecar container.

NO.71 You have a Deployment named ‘worker-deployment’ with 10 replicas of a worker container. You need to implement a rolling update strategy that allows for a maximum of 3 pods to be unavailable at any given time during the update process. You also want to ensure that the update process is completed within a specified timeout of 10 minutes. If the update fails to complete within the timeout, the deployment should revert to the previous version. Additionally, you want to implement a pause functionality to temporarily halt the rolling update process.

NO.72 Score: 4%

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

NO.73 Get list of all the pods showing name and namespace with a jsonpath expression.