Updated Linux Foundation CKAD Dumps – Check Free CKAD Exam Dumps (2026) [Q47-Q62]

Updated Linux Foundation CKAD Dumps – Check Free CKAD Exam Dumps (2026)

Updated CKAD exam with Linux Foundation Real Exam Questions

Linux Foundation Certified Kubernetes Application Developer (CKAD) certification is a professional certification that validates the skills and knowledge of a developer in designing, building, configuring, and deploying applications using Kubernetes. Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. The CKAD certification is designed for developers who are proficient in Kubernetes and have experience in developing, deploying, and managing containerized applications.

NEW QUESTION # 47
You have a microservice application that consists of two components: a web server (using Nginx) and a database (using PostgreSQL). The web server needs to access the database through a local connection, but due to network security restrictions, the web server cannot connect to the database directly. Describe how you can utilize a sidecar container to resolve this issue and ensure the database connection is secure.

Answer:

Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a Sidecar Container:
- Define a new container in your Deployment's 'spec-template-spec-containers' array, alongside the existing Nginx container. This new container will house the necessary tools for facilitating a secure database connection.
- Name this container appropriately, for example, 'database-proxy'
- Choose an image that contains the required software for database connection, such as 'postgres' or 'postgresqr
- Use a sidecar pattern in the Deployment YAML file. You can specify the sidecar in the container array in the Pod specification:

2. Database Connection Configuration: - Configure the sidecar container to connect to the database. - Establish a connection using the database user credentials and connection string. - If you use a secure connection, ensure that the certificates and private keys are accessible to the sidecar container. 3. Communication Between Containers: - Configure your web server container to communicate with the sidecar container. - Use environment variables to specify the hostname and port of the sidecar container, enabling the web server to connect to the database proxy within the pod. 4. Volume Sharing: - Optionally, share a volume between the web server and the sidecar container to facilitate shared data access, such as database configuration files. 5. Deploy the Deployment: - Apply the updated Deployment YAML file to your Kubernetes cluster using 'kubectl apply -f my-app.yaml' 6. Test the Application: - Access your web server application and confirm that it successfully connects to the database through the sidecar container.

NEW QUESTION # 48

Context
It is always useful to look at the resources your applications are consuming in a cluster.
Task
* From the pods running in namespace cpu-stress , write the name only of the pod that is consuming the most CPU to file /opt/KDOBG030l/pod.txt, which has already been created.

Answer:

Explanation:
See the solution below.
Explanation
Solution:

NEW QUESTION # 49
You are developing a new application that requires access to multiple services running in different namespaces. To simplify the configuration and ensure that the application can easily discover these services, you want to use a ServiceAccount with a cluster-scoped Role that grants access to services across namespaces.

Answer:

Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a ClusterRole:
- Create a ClusterRole that grants access to the required services in all namespaces

2. Create a ClusterR01e3inding: - Create a ClusterRole8inding to bind the ClusterRole to the ServiceAccount:

3. Create a ServiceAccount - Create a ServiceAccount in the namespace where the application is deployed:

4. Apply the Configuration: - Apply the ClusterRole, ClusterRoleBinding, and ServiceAccount using 'kL1bectl apply -f: bash kubectl apply -f access-services-cluster-role yaml kubectl apply -f access-services-cluster-role-binding.yaml kubectl apply -f my-app-sa.yaml 5. Configure the Application: - Ensure that the applications pod is using the created ServiceAccount

6. Test the Application: - Run the application and verify that it can successfully access the services in different namespaces. ,

NEW QUESTION # 50
Exhibit:

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:
* Add the func=webFrontEnd key/value label to the pod template metadata to identify the pod for the service definition
* Have 4 replicas
Next, create ana deploy in namespace kdsn00l01 a service that accomplishes the following:
* Exposes the service on TCP port 8080
* is mapped to me pods defined by the specification of kdsn00l01-deployment
* Is of type NodePort
* Has a name of cherry

A. Solution:
B. Solution:

Answer: B

NEW QUESTION # 51
Context

Context
A project that you are working on has a requirement for persistent data to be available.
Task
To facilitate this, perform the following tasks:
* Create a file on node sk8s-node-0 at /opt/KDSP00101/data/index.html with the content Acct=Finance
* Create a PersistentVolume named task-pv-volume using hostPath and allocate 1Gi to it, specifying that the volume is at /opt/KDSP00101/data on the cluster's node. The configuration should specify the access mode of ReadWriteOnce . It should define the StorageClass name exam for the PersistentVolume , which will be used to bind PersistentVolumeClaim requests to this PersistenetVolume.
* Create a PefsissentVolumeClaim named task-pv-claim that requests a volume of at least 100Mi and specifies an access mode of ReadWriteOnce
* Create a pod that uses the PersistentVolmeClaim as a volume with a label app: my-storage-app mounting the resulting volume to a mountPath /usr/share/nginx/html inside the pod

Answer:

Explanation:
Solution:

NEW QUESTION # 52
You are deploying a web application with a separate database container. You need to implement a proxy container that handles requests from the web server and forwards them to the database container. The proxy container should also log all incoming requests to a dedicated log file within the Pod.

Answer:

Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Define the Pod YAML: Create a Pod YAML file that includes the web server, database, and proxy containers.

2. Configure the Proxy Container: Choose a suitable proxy container image (e.g., Nginx, HAProxy) and configure it to forward requests from port 8080 to the database container on port 5432 3. Implement Logging: Configure the proxy container to log incoming requests to the '/var/log/proxy' directory. You can use the proxy container's built- in logging facilities or install a separate logging agent within the container. 4. Deploy the Pod: Apply the Pod YAML using ' kubectl apply -f my-app-pod_yaml' 5. Verify Functionality: Access the web server container on port 80 and ensure requests are forwarded to the database container Check the log file ' Ivar/log/proxys to verify that requests are being logged. Note: This solution demonstrates using a proxy container to manage communication between different containers within a Pod. You can customize the proxy's configuration based on your specific application's requirements.,

NEW QUESTION # 53
You are deploying a new application named 'streaming-services that requires 7 replicas. You want to implement a rolling update strategy that allows for a maximum of two pods to be unavailable at any given time. However, you need to ensure that the update process is triggered automatically whenever a new image is pusned to the Docker Hub repository 'streaming/streaming-service:latest'.

Answer:

Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
I). Update the Deployment YAMI-:
- Update the 'replicas' to 7.
- Define 'maxunavailable: 2" and 'maxSurge: (Y in the 'strategy.rollingUpdate' section.
- Configure a 'strategy.types to 'Rollingl_lpdates to trigger a rolling update when the deployment is updated.
- Add a 'spec-template.spec.imagePullPolicy: Always' to ensure that the new image is pulled even if it exists in the pod's local cache.

2. Create the Deployment: - Apply the updated YAML file using 'kubectl apply -f streaming-service-deployment-yamr 3. Verify the Deployment - Check the status of the deployment using 'kubectl get deployments streaming-service-deployment to confirm the rollout and updated replica count. 4. Trigger the Automatic Update: - Push a new image to the 'streaming/streaming-service:latest' Docker Hub repository. 5. Monitor the Deployment - Use 'kubectl get pods -l app=streaming-service' to monitor the pod updates during the rolling update process. You will observe that two pods are terminated at a time, while two new with the updated image are created. 6. Check for Successful Update: - Once the deployment is complete, use 'kubectl describe deployment streaming-service-deployment' to see that the 'updatedReplicas' field matches the 'replicas' field, indicating a successful update.

NEW QUESTION # 54
Refer to Exhibit.

Set Configuration Context:
[student@node-1] $ | kubectl
Config use-context k8s
Context
A user has reported an aopticauon is unteachable 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:
<namespace>/<pod>

The output file has already been created
* 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
* Fix the issue.

Answer:

Explanation:
To find the broken pod and store its name and namespace to /opt/KDOB00401/broken.txt, you can use the kubectl get pods command and filter the output by the status of the pod.
kubectl get pods --field-selector=status.phase=Failed -o jsonpath='{.items[*].metadata.namespace}/{.items[*].metadata.name}' > /opt/KDOB00401/broken.txt This command will list all pods with a status of Failed and output their names and namespaces in the format <namespace>/<pod>. The output is then written to the /opt/KDOB00401/broken.txt file.
To store the associated error events to a file /opt/KDOB00401/error.txt, you can use the kubectl describe command to retrieve detailed information about the pod, and the grep command to filter the output for error events.
kubectl describe pods <pod-name> --namespace <pod-namespace> | grep -i error -B5 -A5 > /opt/KDOB00401/error.txt Replace <pod-name> and <pod-namespace> with the name and namespace of the broken pod you found in the previous step.
This command will output detailed information about the pod, including error events. The grep command filters the output for lines containing "error" and also prints 5 lines before and after the match.
To fix the issue, you need to analyze the error events and find the root cause of the issue.
It could be that the application inside the pod is not running, the container image is not available, the pod has not enough resources, or the liveness probe configuration is incorrect.
Once you have identified the cause, you can take appropriate action, such as restarting the application, updating the container image, increasing the resources, or modifying the liveness probe configuration.
After fixing the issue, you can use the kubectl get pods command to check the status of the pod and ensure

NEW QUESTION # 55
Context

Task:
A Dockerfile has been prepared at -/human-stork/build/Dockerfile
1) Using the prepared Dockerfile, build a container image with the name macque and lag 3.0. You may install and use the tool of your choice.

2) Using the tool of your choice export the built container image in OC-format and store it at -/human stork/macque 3.0 tar

Answer:

Explanation:
Solution:

NEW QUESTION # 56
You are running a multi-container application on Kubernetes, and you need to update the image of a specific container within the pod without affecting the other containers. You are using a Deployment resource to manage the pods. How can you achieve this update using imperative commands?

Answer:

Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Identify the Pod:
- Use 'kubectl get pods -l to list the pods managed by your deployment. Replace
- Identify the pod that needs the container image update.
2. Identify the Container:
- Use ' kubectl describe pod to display the pod's details, including its containers.
- Note the name of the container you want to update.
3. Update the Container Image:
with the label you've defined for your deployment.
- Use 'kubectl exec -it -container bash' to create an interactive shell within the specified container.
- Inside the shell, update the image for the container using 'docker pull ' (Replace with the new container image you want to use).
- Exit the shell using 'exit
4. Restart the Container:
- Use 'kubectl exec -it -container bash' to access the container again.
- Run 'docker restan to restart the container with the new image.
- Exit the shell using 'exit'.
5. Verify the Image Update:
- Run 'kubectl describe pod to check the updated pod details. Verify that the container image iS now the new one you pulled.
Note: This approach updates the container image in the existing pod. If you want to apply the update to all pods managed by the Deployment, you'll need to update the Deployment configuration itself. ,

NEW QUESTION # 57

Given a container that writes a log file in format A and a container that converts log files from format A to format B, create a deployment that runs both containers such that the log files from the first container are converted by the second container, emitting logs in format B.
Task:
* Create a deployment named deployment-xyz in the default namespace, that:
*Includes a primary
lfccncf/busybox:1 container, named logger-dev
*includes a sidecar Ifccncf/fluentd:v0.12 container, named adapter-zen
*Mounts a shared volume /tmp/log on both containers, which does not persist when the pod is deleted
*Instructs the logger-dev
container to run the command

which should output logs to /tmp/log/input.log in plain text format, with example values:

* The adapter-zen sidecar container should read /tmp/log/input.log and output the data to /tmp/log/output.* in Fluentd JSON format. Note that no knowledge of Fluentd is required to complete this task: all you will need to achieve this is to create the ConfigMap from the spec file provided at /opt/KDMC00102/fluentd-configma p.yaml , and mount that ConfigMap to /fluentd/etc in the adapter-zen sidecar container See the solution below.

Answer:

Explanation:
Solution:

NEW QUESTION # 58

Set Configuration Context:
[student@node-1] $ | kubectl
Config use-context k8s
Task
You have rolled out a new pod to your infrastructure and now you need to allow it to communicate with the web and storage pods but nothing else. Given the running pod kdsn00201 -newpod edit it to use a network policy that will allow it to send and receive traffic only to and from the web and storage pods.

Answer:

Explanation:
See the solution below.
Explanation:
To allow a pod to send and receive traffic only to and from specific pods, you can use network policies in Kubernetes.
First, you will need to create a network policy that defines the allowed traffic. You can create a network policy yaml file with the following rules:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: newpod-network-policy
namespace: default
spec:
podSelector:
matchLabels:
app: kdsn00201-newpod
ingress:
- from:
- podSelector:
matchLabels:
app: web
- podSelector:
matchLabels:
app: storage
This policy will only allow incoming traffic to the pod with the label app=kdsn00201-newpod from pods with the label app=web or app=storage. If you have different labels on your web and storage pods please update the matchLabels accordingly.
Once you have created the network policy, you can apply it to the cluster by running the following command:
kubectl apply -f <network-policy-file>.yaml
This will apply the network policy to the cluster, and the newpod will only be able to send and receive traffic to and from the web and storage pods.
Please note that, NetworkPolicy resource is not available by default, you need to enable the NetworkPolicy feature on your Kubernetes cluster. This feature is enabled by default on some clusters and must be explicitly enabled on others. You can check if NetworkPolicy is available by running the command kubectl api-versions
| grep networking
Also, you need to ensure that the pods that you want to allow traffic to and from are running on the same namespace.

NEW QUESTION # 59
You are designing a microservice architecture where a frontend application needs to communicate with multiple backend services. The services are deployed as Pods in a Kubernetes cluster- To streamline communication and security, you decide to implement a sidecar proxy pattern Explain the benefits of using a sidecar proxy in this scenario and illustrate how you would implement it using a container image like Envoy Proxy.

Answer:

Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Understand Sidecar Proxy Pattern:
- In the sidecar proxy pattern, a proxy container runs alongside your main application container within the same Pod.
- The proxy acts as an intermediary, handling network tratfic between your application and other services.
2. Benefits of Using a Sidecar Proxy:
- Traffic Management:
- Routing requests to different backend services.
- Load balancing across multiple instances ot a service.
- Security:
- Enforcing access control and authentication.
- Handling SSL termination.
- Observability:
- Monitoring and logging network traffic.
- Simplified Development:
- Separating networking concerns from application logic.
3. Implementing with Envoy Proxy:
- Choose Envoy Proxy:
- Envoy is a popular open-source proxy designed for high-performance network communication.
- Create a Deployment YAML:
- Define a Deployment for your application, including a main container for your application code and a sidecar container for Envoy Proxy.

4. Configure Envoy: - Create a ConfigMap: - Create a ConfigMap to hold the Envoy configuration (envoy-yaml). - Define the routes, listeners, and clusters for your services.

5. Deploy the Configuration: - Apply the Deployment and ConfigMap using 'kubectl apply -f deployment.yaml' and 'kubectl apply -f configmap.yaml' 6. Test tne Setup: - Access your trontend application from outside the cluster. - Verity that traffic is routed correctly to the backend services through the Envoy proxy. 7. Optional: Service Discovery: - For more dynamic environments, you can integrate Envoy with service discovery mechanisms like Kubernetes Service or Consul to automatically update its configuration based on service changes. This configuration assumes that your backend services are named "servicel " and "service2" with ports 8080. Adjust the configuration based on your specific services and their port numbers.,

NEW QUESTION # 60
You have a Kubernetes deployment named 'wordpress-deployment' running multiple instances of a WordPress application. You want to implement a rolling update strategy with a 'maxSurge' of 1 and 'maxi-Jnavailable' of O. Additionally, you need to ensure that the update process is automatically triggered when a new image is pushed to the Docker Hub repository 'wordpress-image:latests. Implement a Kustomization file to achieve this.

Answer:

Explanation:
See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a 'kustomization.yamr file in your desired directory.

2. Create a 'deployment-yamr file (or use an existing one) with the following structure.

3. Create a 'patch.yamr file with the following content to configure rolling update and automatic updates:

4. Apply the Kustomization: bash kubectl apply -k - The 'kustomization.yaml file defines the resources (the 'deployment.yamr file) and the patches to apply. - The 'deployment.yamr file contains the base configuration for the deployment. - The 'patch.yamr file applies a strategic merge patch to the deployment, configuring rolling updates and automatic updates triggered by new images. - The 'maxSurgew and 'maxunavailable' settings in the 'patch.yamr define the maximum number ot pods that can be added or removed during the update process. - The 'imagePullPolicy: AlwayS ensures that the new image is pulled from Docker Hub even if it exists in the pod's local cache, triggering the update.

NEW QUESTION # 61

Task:
A Dockerfile has been prepared at -/human-stork/build/Dockerfile
1) Using the prepared Dockerfile, build a container image with the name macque and lag 3.0. You may install and use the tool of your choice.

2) Using the tool of your choice export the built container image in OC-format and store it at -/human stork/macque 3.0 tar See the solution below.