Name: Certified Kubernetes Administrator
Brand: ValidExamDumps
SKU: CKA
Price: 20 USD
Availability: InStock
Rating: 4.8 (148 reviews)

Free Linux Foundation CKA Exam Actual Questions

The questions for CKA were last updated On Apr 22, 2025

At ValidExamDumps, we consistently monitor updates to the Linux Foundation CKA exam questions by Linux Foundation. Whenever our team identifies changes in the exam questions,exam objectives, exam focus areas or in exam requirements, We immediately update our exam questions for both PDF and online practice exams. This commitment ensures our customers always have access to the most current and accurate questions. By preparing with these actual questions, our customers can successfully pass the Linux Foundation Certified Kubernetes Administrator exam on their first attempt without needing additional materials or study guides.

Other certification materials providers often include outdated or removed questions by Linux Foundation in their Linux Foundation CKA exam. These outdated questions lead to customers failing their Linux Foundation Certified Kubernetes Administrator exam. In contrast, we ensure our questions bank includes only precise and up-to-date questions, guaranteeing their presence in your actual exam. Our main priority is your success in the Linux Foundation CKA exam, not profiting from selling obsolete exam questions in PDF or Online Practice Test.

Question No. 1

Print pod name and start time to ''/opt/pod-status'' file

AExplanation:
kubect1 get pods -o=jsonpath='{range
.items[*]}{.metadata.name}{'\t'}{.status.podIP}{'\n'}{end}'

Show Answer

Correct Answer: A

Question No. 2

Create a persistent volume with name app-data, of capacity 2Gi and access mode ReadWriteMany. The type of volume is hostPath and its location is /srv/app-data.

AExplanation:
solution
Persistent Volume
A persistent volume is a piece of storage in a Kubernetes cluster. PersistentVolumes are a cluster-level resource like nodes, which don't belong to any namespace. It is provisioned by the administrator and has a particular file size. This way, a developer deploying their app on Kubernetes need not know the underlying infrastructure. When the developer needs a certain amount of persistent storage for their application, the system administrator configures the cluster so that they consume the PersistentVolume provisioned in an easy way.
Creating Persistent Volume
kind: PersistentVolume
apiVersion: v1
metadata:
name:app-data
spec:
capacity: # defines the capacity of PV we are creating
storage: 2Gi #the amount of storage we are tying to claim
accessModes: # defines the rights of the volume we are creating
- ReadWriteMany
hostPath:
path: '/srv/app-data' # path to which we are creating the volume
Challenge
Create a Persistent Volume named app-data, with access mode ReadWriteMany, storage classname shared, 2Gi of storage capacity and the host path /srv/app-data.

2. Save the file and create the persistent volume.

3. View the persistent volume.

Our persistent volume status is available meaning it is available and it has not been mounted yet. This status will change when we mount the persistentVolume to a persistentVolumeClaim.
PersistentVolumeClaim
In a real ecosystem, a system admin will create the PersistentVolume then a developer will create a PersistentVolumeClaim which will be referenced in a pod. A PersistentVolumeClaim is created by specifying the minimum size and the access mode they require from the persistentVolume.
Challenge
Create a Persistent Volume Claim that requests the Persistent Volume we had created above. The claim should request 2Gi. Ensure that the Persistent Volume Claim has the same storageClassName as the persistentVolume you had previously created.
kind: PersistentVolume
apiVersion: v1
metadata:
name:app-data
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 2Gi
storageClassName: shared
2. Save and create the pvc
njerry191@cloudshell:~ (extreme-clone-2654111)$ kubect1 create -f app-data.yaml
persistentvolumeclaim/app-data created
3. View the pvc

4. Let's see what has changed in the pv we had initially created.

Our status has now changed from available to bound.
5. Create a new pod named myapp with image nginx that will be used to Mount the Persistent Volume Claim with the path /var/app/config.
Mounting a Claim
apiVersion: v1
kind: Pod
metadata:
creationTimestamp: null
name: app-data
spec:
volumes:
- name:congigpvc
persistenVolumeClaim:
claimName: app-data
containers:
- image: nginx
name: app
volumeMounts:
- mountPath: '/srv/app-data '
name: configpvc

Show Answer

Correct Answer: A

Question No. 3

Create a busybox pod that runs the command ''env'' and save the output to ''envpod'' file

AExplanation:
kubectl run busybox --image=busybox --restart=Never ---rm -it -- env > envpod.yaml

Show Answer

Correct Answer: A

Question No. 4

List all the pods sorted by name

AExplanation:
kubectl get pods --sort-by=.metadata.name

Show Answer

Correct Answer: A

Question No. 5

Create a namespace called 'development' and a pod with image nginx called nginx on this namespace.

AExplanation:
kubectl create namespace development
kubectl run nginx --image=nginx --restart=Never -n development

Show Answer

Correct Answer: A