CKA Mock test question 4

There is an existing persistent volume called orange-pv-cka13-trb. A persistent volume claim called orange-pvc-cka13-trb is created to claim storage from orange-pv-cka13-trb.However, this PVC is stuck in a Pending state. As of now, there is no data in the volume.Troubleshoot and fix this issue, making sure that orange-pvc-cka13-trb PVC is in Bound state.|

Troubleshooting:
There was a mismatch of request in pv(100mi) and pvc(150mi). I updated pvc to 150mi and pvc was in bound state also.|
But still my answer is wrong. Why?|

Hi @uzmashafi061,

We need additional information to debug the issue. Please provide us the link to the Mock exam and also check the solution provided at the end of the mock.

Regard

Lab- CKA Mock Exam 2 - KodeKloud.

I checked the answer but still have doubt because they made changes in PVC(changed value from 150MI to 100MI) and i made changes in PV (changed value from 100MI to 150MI).

Hi @uzmashafi061,

We need to update the PVC to align it with a size less than or equal to the size of the PV in this case 100Mi.

After the modification, you need to delete the existed PVC and create a new with the new volume

> kubectl get pvc orange-pvc-cka13-trb -o yaml > pvc-to-update.yaml 

## Edit the file pvc-to-update.yaml to adapt the size (LE 100Mi)

> kubectl delete pvc orange-pvc-cka13-trb ### delete the PVC

> kubectl create -f pvc-to-update.yaml ### recreate the PVC 

thanks for the soln but one question here, why cant we make changes in PV(by changing its value from 100MI to 150MI)?

I also faced this every time with this question. For change requested volume i recreated PVC with asked Mi volume then I create it. It correctly created and shown in bound state. I change nothing else this problem is might be from result evaluation.

I get this question in different mock exam, Recently I get it in exam #10 of Ultimate Certified Kubernetes Administrator (CKA) Mock Exam Series

I am also receiving an unexpected failure for this question. I captured the pvc yaml in a file, edited the storage request from 150Mi to 100Mi, deleted the pvc and recreated it. The status changes to bound to the expected PV. So far I’ve encountered this question, with an unexpected failure, in Mock Exams 3 and 4.

k get pvc orange-pvc-cka13-trb -o yaml > pvc.yaml
vi pvc.yaml

Edit the storage value to 100Mi

k replace --force -f pvc.yaml

image

Hi Alistair, this is one the questions where it’s not clear if we have to change PV or PVC.

If we change the PVC to 100Mi the question is marked as correct.

If we change PV to 150Mi which also fixes the issue the question is marked as incorrect.

There’s another one involving crashed pods where it’s the other way around. Changing the PV the question is marked as correct, changing PVC to fix the issue gets an incorrect answer

In the above question it is the PVC that is expected to be changed.

It is asking for you to make the PVC bind to the existing volume.

1 Like

Hi @Alistair_KodeKloud

It seems that there are some glitches in the Mock Exam sandboxes.
I got this issue with PVC too, even if I did everything right - resized and recreated pvc, without touching pv.
In the same time I also get reported that another question was not correct (which was also not true). However after couple re-checks of exam results, finally all questions got green.