CKA Free Certification Exam Material from TestKingIT with 68 Questions [Q27-Q47]

By adminOn May 26, 2023

4.7/5 - (6 votes)

CKA Free Certification Exam Material from TestKingIT with 68 Questions

Use Real CKA – 100% Cover Real Exam Questions

The CKA certification is widely recognized in the industry and is a valuable asset for IT professionals. The certification demonstrates that one has the skills and knowledge to manage Kubernetes clusters effectively. CKA certified professionals are in high demand, and the certification can lead to better job opportunities and higher salaries. The certification is also a stepping stone to more advanced Kubernetes certifications, such as the Certified Kubernetes Security Specialist (CKS) and the Certified Kubernetes Application Developer (CKAD).

NEW QUESTION 27
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 be persistent.

NEW QUESTION 28
Create a Pod with three busy box containers with commands “ls; sleep 3600;”, “echo Hello World; sleep 3600;” and “echo this is the third container; sleep 3600” respectively and check the status

// first create single container pod with dry run flag
kubectl run busybox –image=busybox –restart=Always –dry-run
-o yaml — bin/sh -c “sleep 3600; ls” > multi-container.yaml
// edit the pod to following yaml and create it
apiVersion: v1
kind: Pod
metadata:
labels:
run: busybox
name: busybox
spec:
containers:
– args:
– bin/sh
– -c
– ls; sleep 3600
– echo Hello world; sleep 3600
image: busybox
name: busybox-container-2
– args:
– bin/sh
– -c
– echo this is third container; sleep 3600
image: busybox
name: busybox-container-3
restartPolicy: Always
// Verify
Kubectl get pods

// first create single container pod with dry run flag
kubectl run busybox –image=busybox –restart=Always –dry-run
-o yaml — bin/sh -c “sleep 3600; ls” > multi-container.yaml
// edit the pod to following yaml and create it
apiVersion: v1
kind: Pod
metadata:
labels:
run: busybox
name: busybox
spec:
containers:
– args:
– bin/sh
– -c
– ls; sleep 3600
image: busybox
name: busybox-container-1
– args:
– bin/sh
– -c
– echo Hello world; sleep 3600
image: busybox
name: busybox-container-2
– args:
– bin/sh
– -c
– echo this is third container; sleep 3600
image: busybox
name: busybox-container-3
restartPolicy: Always
// Verify
Kubectl get pods

NEW QUESTION 29
Score:7%

Task
Create a new PersistentVolumeClaim
* Name: pv-volume
* Class: csi-hostpath-sc
* Capacity: 10Mi
Create a new Pod which mounts the PersistentVolumeClaim as a volume:
* Name: web-server
* Image: nginx
* Mount path: /usr/share/nginx/html
Configure the new Pod to have ReadWriteOnce access on the volume.
Finally, using kubectl edit or kubectl patch expand the PersistentVolumeClaim to a capacity of 70Mi and record that change.

NEW QUESTION 30
A bootstrap USB flash drive has been prepared using a Linux workstation to load the initial configuration of a Palo Alto Networks firewall. The USB flash drive was formatted using file system ntfs and the initial configuration is stored in a file named init-cfg.txt.
The contents of Init-cfg.txt in the USB flash drive are as follows:
type=static
ip-address=10.5.107.19
default-gateway=10.5.107.1
netmask=255.255.255.0
Ipv6-address=2001:400:100::1/64
ipv6-default-gateway=2001:400:100::2
hostname=Ca-FW-DC1
panorama-server=10.5.107.20
panorama-server-2=10.5.107.21
tplname=FINANCE TG4
dgname=finance_dg
dns-primary=10.5.6.6
op-command-modes multi-vsys.jumbo-frame
dhcp-send-hostname=no
dhcp-send-client-id=no
dhcp-accept-server-hostname=no
dhcp-accept-server-domain=no
The USB flash drive has been inserted in the firewalls’ USB port, and the firewall has been powered on.Upon boot, the firewall fails to begin the bootstrapping process. The failure is caused because:

There must be commas between the parameter names and their values instead of the equal symbols

nit-cfg bit is an incorrect filename the correct filename should be init-ofg.xml

The USB must be formatted using the ext4 file system

The USB drive has been formatted with an unsupported file system

The bootstrap.xml file is a required file, but it is missing

NEW QUESTION 31
Pause the rollout of the deployment

NEW QUESTION 32
Get IP address of the pod – “nginx-dev”

Kubect1 get po -o wide
Using JsonPath
kubect1 get pods
.items[*]}{.metadata.name}{“t”}{.status.podIP}{“n”}{end}’

Kubect1 get po -o wide
Using JsonPath
kubect1 get pods -o=jsonpath='{range
.items[*]}{.metadata.name}{“t”}{.status.podIP}{“n”}{end}’

NEW QUESTION 33
Create a secret mysecret with values user=myuser and password=mypassword

kubectl create secret generic my-secret –fromliteral=username=user –from-literal=password=mypassword
// Verify
kubectl get secret –all-namespaces
kubectl get secret generic my-secret -o yaml

kubectl create secret generic my-secret –fromliteral=username=user –from-literal=password=mypassword
// Verify
kubectl get secret generic my-secret -o yaml

NEW QUESTION 34
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.

NEW QUESTION 35
List all the pods sorted by name

NEW QUESTION 36
Create a pod that echo “hello world” and then exists. Have the pod deleted automatically when it’s completed

NEW QUESTION 37
Create a Kubernetes secret asfollows:
* Name: super-secret
* password: bob
Create a pod namedpod-secrets-via-file Image, which mounts a secret namedsuper-secretat
/secrets.
Create a second pod namedpod-secrets-via-env Image, which exportspasswordas CONFIDENTIAL

NEW QUESTION 38
List all the events sorted by timestamp and put them into file.log and verify

kubectl get events –sort-by=.metadata.creationTimestamp
kubectl get events –sort-by=.metadata.creationTimestamp >
test-file.log
cat test-file.log

kubectl get events –sort-by=.metadata.creationTimestamp
// putting them into file.log
kubectl get events –sort-by=.metadata.creationTimestamp >
cat test-file.log

kubectl get events –sort-by=.metadata.creationTimestamp
// putting them into file.log
kubectl get events –sort-by=.metadata.creationTimestamp >
test-file.log
cat test-file.log

NEW QUESTION 39
Label a node as app=test and verify

NEW QUESTION 40
Scale the deployment to 5 replicas

NEW QUESTION 41
Scale the deployment webserver to

NEW QUESTION 42
Create a PersistentVolumeClaim of at least 3Gi storage and access mode ReadWriteOnce and verify status is Bound

vim task-pv-claim.yaml
apiVersion: v2
kind: PersistentVolumeClaim
metadata:
name: task-pv-claim
spec:
storageClassName: “”
accessModes:
– ReadWriteOnce
resources:
requests:
storage: 4Gi
kubectl apply -f task-pv-claim.yaml
//Verify
kubectl get pv
NAME CAPACITY ACCESS
MODES RECLAIM POLICY STATUS CLAIM
STORAGECLASS REASON AGE
task-pv-volume 4Gi RWO
Retain Bound default/task-pv-claim
6m16s
kubectl get pvc
NAME STATUS VOLUME
CAPACITY ACCESS MODES STORAGECLASS AGE
task-pv-claim Bound task-pv-volume
5Gi RWO 6s

vim task-pv-claim.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: task-pv-claim
spec:
storageClassName: “”
accessModes:
– ReadWriteOnce
resources:
requests:
storage: 3Gi
kubectl apply -f task-pv-claim.yaml
//Verify
kubectl get pv
NAME CAPACITY ACCESS
MODES RECLAIM POLICY STATUS CLAIM
STORAGECLASS REASON AGE
task-pv-volume 5Gi RWO
Retain Bound default/task-pv-claim
6m16s
kubectl get pvc
NAME STATUS VOLUME
CAPACITY ACCESS MODES STORAGECLASS AGE
task-pv-claim Bound task-pv-volume
5Gi RWO 6s

NEW QUESTION 43
Create a Cronjob with busybox image that prints date and hello from kubernetes cluster message for every minute

CronJob Syntax:
* –> Minute
* –> Hours
* –> Day of The Month
* –> Month
* –> Day of the Week
*/1 * * * * –> Execute a command every one minutes.
vim date-job.yaml
apiVersion: batch/v1beta1
kind: CronJob
metadata:
name: date-job
spec:
schedule: “*/1 * * * *”
jobTemplate:
spec:
template:
spec:
containers:
– name: hello
image: busybox
args:
– /bin/sh
– -c
– date; echo Hello from the Kubernetes cluster
restartPolicy: OnFailure
kubectl apply -f date-job.yaml
//Verify
kubectl get cj date-job -o yaml

CronJob Syntax:
* –> Minute
* –> Hours
* –> Day of The Month
* –> Month
* –> Day of the Week
*/1 * * * * –> Execute a command every one minutes.
vim date-job.yaml
apiVersion: batch/v1beta1
kind: CronJob
metadata:
name: date-job
spec:
schedule: “*/1 * * * *”
jobTemplate:
spec:
template:
– /bin/sh
– -c
– date; echo Hello from the Kubernetes cluster
restartPolicy: OnFailure
kubectl apply -f date-job.yaml
//Verify
kubectl get cj date-job -o yaml

NEW QUESTION 44
Check the Image version of nginx-dev pod using jsonpath

NEW QUESTION 45
List the nginx pod with custom columns POD_NAME and POD_STATUS

NEW QUESTION 46
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 further.

NEW QUESTION 47
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.