MENU
You want to mount external storage to a particular filesystem path in a
container in a Kubernetes pod.
What is the correct set of objects to use for this?
Suggested Answer: C
Get Premium DCA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
MA
Mabel
11 months ago
Not sure about that, seems a bit complicated.
LE
Lettie
11 months ago
Definitely D, it’s the standard approach!
MA
Martina
12 months ago
Wait, isn't it just a persistentVolumeClaim we need?
CH
Chantell
12 months ago
I think A sounds right too.
DA
Dalene
12 months ago
Option D is the way to go!
TA
Tamala
1 year ago
I thought the storageClass was more about provisioning than directly related to the pod, so I'm leaning towards D as well.
SA
Sarah
1 year ago
I feel like option A could be correct too, but I can't recall if the persistentVolume should be directly in the pod spec.
DA
Daniela
1 year ago
I remember practicing a question similar to this, and I think the persistentVolumeClaim is crucial for binding to the persistentVolume.
TH
Thurman
1 year ago
I think it might be option D, but I'm not entirely sure about how the persistentVolumeClaim works in this context.
MA
Maryann
1 year ago
Ugh, I hate these finance questions. The formulas always trip me up. Maybe I can at least eliminate a couple of the answer choices and take an educated guess.
SC
Scarlet
1 year ago
Hmm, this seems like a tricky one. I'll need to think carefully about the different options and how they might impact the application.
PH
Phuong
1 year ago
Wait, are we supposed to actually understand this stuff? I thought this was a test of our ability to guess randomly. Time to put my luck to the test!
VE
Veronika
1 year ago
Option D, definitely. I've used this setup before and it works like a charm. Gotta love that Kubernetes storage abstraction!
IO
Iola
1 year ago
User 3: Yeah, Kubernetes storage abstraction makes it so much easier to manage storage in pods.
KA
Karan
1 year ago
User 2: Agreed, I've used that setup before and it worked really well.
NI
Niesha
1 year ago
User 1: I think option D is the way to go for mounting external storage in a Kubernetes pod.
PO
Polly
1 year ago
Haha, this question is a real brain-teaser! Kubernetes storage management is no joke. I'm going to have to think this one through carefully.
NI
Nilsa
1 year ago
Kelvin: Definitely, Kubernetes storage management can be tricky but it's important to understand the correct setup for mounting external storage.
KE
Kelvin
1 year ago
User 2: That makes sense, it's important to have the persistentVolumeClaim bound to the volume defined by a storageClass.
JA
Jaleesa
1 year ago
User 1: I think the correct set of objects to use is A) a persistentVolume in the pod specification, populated with a persistentVolumeClaim which is bound to a volume defined by a storageClass.
NA
Nan
1 year ago
I don't know, Option A looks pretty good too. A persistentVolumeClaim bound to a volume defined by a storageClass seems like a valid approach.
DE
Devon
1 year ago
User 4: Let's go with Option A then, it seems like the best choice.
JE
Jess
1 year ago
User 3: I'm not sure, but Option A does seem like a valid approach.
IZ
Izetta
1 year ago
User 2: Yeah, a persistentVolumeClaim bound to a volume defined by a storageClass makes sense.
AL
Alise
1 year ago
User 1: I think Option A is the correct one.
JO
Joni
1 year ago
User 4: Let's go with Option A then, it seems like the best choice.
EA
Earleen
1 year ago
User 3: I'm not sure, but Option A does seem like a valid approach.
MA
Martha
1 year ago
User 3: I agree, that seems like the right approach for mounting external storage in a Kubernetes pod.
SA
Salena
1 year ago
User 2: Yeah, a persistentVolumeClaim bound to a volume defined by a storageClass makes sense.
VA
Valentin
1 year ago
User 1: I think Option A is the correct one.
EL
Elena
1 year ago
User 2: Yeah, using a persistentVolumeClaim bound to a volume defined by a storageClass makes sense.
MI
Michell
1 year ago
User 1: I think Option A is the correct one.
ME
Merissa
1 year ago
Option D looks correct to me. A persistentVolumeClaim bound to a persistentVolume defined by a storageClass seems like the right way to mount external storage.
JU
Justine
1 year ago
I agree, using a persistentVolumeClaim bound to a persistentVolume defined by a storageClass is the way to go.
CH
Chu
1 year ago
Option D looks correct to me.
BE
Belen
1 year ago
But wouldn't using a persistentVolume directly in the pod specification provide more flexibility and control over the storage?
DI
Diego
2 years ago
I disagree, I believe the correct set of objects to use is D) a volume in the pod specification, populated with a persistentVolumeClaim bound to a persistentVolume defined by a storageClass.
BE
Belen
2 years ago
I think the correct set of objects to use is A) a persistentVolume in the pod specification, populated with a persistentVolumeClaim which is bound to a volume defined by a storageClass.