[Q33-Q48] Pass Linux Foundation Certified Kubernetes Administrator (CKA) Program Exam Exam in First Attempt Guaranteed Updated Dump from Test4Cram!

NEW QUESTION 33
You are running a Kubernetes cluster with a critical application that requires high availability and resilience. You have a Deployment named ‘web-app’ with multiple replicas. Your current DNS setup relies on external DNS providers, but you want to implement CoreDNS within your cluster to enhance DNS resolution performance and reliability. You need to configure CoreDNS to resolve DNS queries for services within the cluster and for external domains.

NEW QUESTION 34
Change the label for one of the pod to env=uat and list all the pods to verify

NEW QUESTION 35
List all persistent volumes sorted bycapacity, saving the fullkubectloutput to
/opt/KUCC00102/volume_list. Usekubectl ‘s own functionality forsorting the output, and do not manipulate it any further.

NEW QUESTION 36
Score: 13%

Task
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.

NEW QUESTION 37
Create a deployment called webapp with image nginx having 5 replicas in it, put the file in /tmp directory with named webapp.yaml

//Create a file using dry run command
kubectl create deploy –image=nginx –dry-run -o yaml >
/tmp/webapp.yaml
// Now, edit file webapp.yaml and update replicas=5
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: webapp
name: webapp
spec:
replicas: 5
selector:
matchLabels:
app: webapp
template:
metadata:
labels:
app: webapp
spec:
containers:
– image: nginx
name: nginx
Note: Search “deployment” in kubernetes.io site , you will get
the page
https://kubernetes.io/docs/concepts/workloads/controllers/deplo
yment/
// Verify the Deployment
kubectl get deploy webapp –show-labels
// Output the YAML file of the deployment webapp
kubectl get deploy webapp -o yaml

//Create a file using dry run command
kubectl create deploy –image=nginx –dry-run -o yaml >
/tmp/webapp.yaml
// Now, edit file webapp.yaml and update replicas=5
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: webapp
name: webapp
spec:
replicas: 5
selector:
matchLabels:
app: webapp
template:
metadata:
labels:
Note: Search “deployment” in kubernetes.io site , you will get
the page
https://kubernetes.io/docs/concepts/workloads/controllers/deplo
yment/
// Verify the Deployment
kubectl get deploy webapp –show-labels
// Output the YAML file of the deployment webapp
kubectl get deploy webapp -o yaml

NEW QUESTION 38
Task Weight: 4%

Task
Schedule a Pod as follows:
* Name: kucc1
* App Containers: 2
* Container Name/Images:
o nginx
o consul

NEW QUESTION 39
You have a deployment that runs multiple replicas of a web server application. You need to ensure that the Deployment always maintains at least 2 replicas available, even if one or more pods are deleted or become unavailable. How can you configure the Deployment to achieve this using the ‘maxUnavailable’ field in the ‘strategy.rollingUpdate’ section?

NEW QUESTION 40
Delete persistent volume and persistent volume claim

NEW QUESTION 41
You are managing a Kubernetes cluster for a company with multiple teams working on different projects. You want to implement RBAC to ensure each team has access only to the resources they need.

NEW QUESTION 42
Resume the rollout of the deployment

NEW QUESTION 43
Check to see how many worker nodes are ready (not including nodes taintedNoSchedule) and write the number to/opt/KUCC00104/kucc00104.txt.

NEW QUESTION 44
Add a taint to node “worker-2” with effect as “NoSchedule” and
list the node with taint effect as “NoSchedule”

// Add taint to node “worker-2”
kubectl taint nodes worker-2 key=value:NoSchedule
.items[*]}{.metadata.name} {.spec.taints[?(
@.effect==’NoSchedule’ )].effect}{“n”}{end}” | awk ‘NF==2
{print $0}’

// Add taint to node “worker-2”
kubectl taint nodes worker-2 key=value:NoSchedule
// Verify
// Using “custom-coloumns” , you can customize which coloumn to
be printed
kubectl get nodes -o customcolumns=NAME:.metadata.name,TAINTS:.spec.taints –no-headers
// Using jsonpath
kubectl get nodes -o jsonpath=”{range
.items[*]}{.metadata.name} {.spec.taints[?(
@.effect==’NoSchedule’ )].effect}{“n”}{end}” | awk ‘NF==2
{print $0}’

NEW QUESTION 45
Score: 7%

Task
Given an existing Kubernetes cluster running version 1.20.0, upgrade all of the Kubernetes control plane and node components on the master node only to version 1.20.1.
Be sure to drain the master node before upgrading it and uncordon it after the upgrade.

You are also expected to upgrade kubelet and kubectl on the master node.

NEW QUESTION 46
You are tasked with setting up a Kubernetes cluster for a company with a strict security policy. They have two different teams: Development and Operations, with distinct access requirements.
The Development team needs read-only access to all resources and the ability to create and manage deployments, pods, and services. The Operations team needs full access to all resources, including cluster management, and the ability to perform actions like scaling, rolling updates, and troubleshooting.
Design a role-based access control (RBAC) configuration using Kubernetes resources (Role, RoleBinding, ClusterRole, ClusterRoleBinding) to grant appropriate access to each team.

NEW QUESTION 47
A Deployment named ‘my-app-deployment’ is experiencing frequent crashes. You suspect that a specific container within the Deployment is causing the crashes. How would you use Kubernetes tools and techniques to isolate and debug the problematic container?

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Examine Pod Logs:
– Use “kubectl logs ‘ (where is the name of a crashing pod) to examine the logs from all containers within the pod. Look for error messages, unusual patterns, or indications of failing processes.
– Analyze the log messages carefully to identify which container is likely causing the crashes.
2. Investigate Pod Events:
– Use “kubectl describe pod ‘ to view the pod’s events.
– Look for events that might indicate a specific container is crashing or encountering issues during startup. Events will include timestamps and reasons for the events.
3. Check Container Resource Limits:
– Use ‘kubectl describe pod to check the resource requests and limits defined for each container within the pod.
– If the limits are too low, the containers might be being throttled or running out of resources, leading to crashes.
4. Use a Debugger:
– If you have access to the application code and a debugger (like a remote debugger in your development environment), you can attach to the problematic container to get more detailed information about its state and execution.
– Use the ‘kubectl exec’ command to access a container’s shell, and then run the debugger.
5. Consider Health Checks:
– Ensure that the containers have proper health checks defined (e.g., liveness probes or readiness probes).
– Health checks can help Kubernetes identify failing containers and restart them or remove them from service.
6. Isolate the Container:
– If you suspect that the container itself is faulty, try isolating it by temporarily disabling the problematic container from the pod. You can do this by either:
– Removing the container from the Pod definition: Temporarily modify the Deployment to remove the problematic container.
– Stopping the container: Use ‘kubectl exec’ to access the pod’s shell, and then stop the container.
7. Monitor and Repeat:
– After isolating the container, monitor the Deployment to see if the crashes stop.
– If the crashes are resolved, the isolated container was likely the cause. You can then focus on troubleshooting the container itself.

NEW QUESTION 48
For this item, you will have to ssh to the nodes ik8s-master-0 and ik8s-node-0 and complete all tasks on these nodes. Ensure that you return to the base node (hostname: node-1) 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.

Leave a Reply Cancel reply