Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

VMware 5V0-23.20 Exam - Topic 7 Question 61 Discussion

Actual exam question for VMware's 5V0-23.20 exam

Question #: 61
Topic #: 7

[All 5V0-23.20 Questions]

How can you remove unreferenced container images from a project in an embedded Registry Service?

ADelete images in Content Library.

BUse kubectl to delete the images.

CDelete the namespace using the vSphere Client.

DPurge a namespace using the vSphere Client.

Show Suggested Answer

Suggested Answer: D, E

by Jess at Jan 13, 2025, 01:15 PM

Limited Time Offer

25%

Off

Get Premium 5V0-23.20 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Goldie

10 months ago

Wait, can you really just delete images like that?

upvoted 0 times

...

Wilda

10 months ago

Deleting the namespace seems like overkill.

upvoted 0 times

...

Dalene

10 months ago

Purging a namespace sounds risky, but effective.

upvoted 0 times

...

Hubert

11 months ago

I think using kubectl is a better option!

upvoted 0 times

...

Jeffrey

11 months ago

You can delete images in the Content Library.

upvoted 0 times

...

Darrin

11 months ago

Purging a namespace sounds familiar, but I can't remember if that's the correct method for removing unreferenced images.

upvoted 0 times

...

Veronika

11 months ago

I feel like deleting images in the Content Library was mentioned in our study materials, but I don't know if that's the right approach here.

upvoted 0 times

...

Nieves

11 months ago

I think we practiced a question similar to this, and it involved using kubectl, but I can't recall the exact command.

upvoted 0 times

...

Vernice

12 months ago

I remember something about using the vSphere Client, but I'm not sure if it's about deleting the namespace or purging it.

upvoted 0 times

...

Denise

12 months ago

I've got this! The key here is that we're dealing with an embedded Registry Service, so the vSphere Client is likely the best tool for the job. Deleting the namespace or purging it should do the trick to remove those unreferenced container images.

upvoted 0 times

...

Lashon

12 months ago

Okay, let me think this through. Since this is about an embedded Registry Service, I'm guessing the vSphere Client might be the way to go. Purging a namespace could be the right solution, but I'll double-check the other options just to be sure.

upvoted 0 times

...

Willodean

12 months ago

Hmm, I'm a bit unsure about this one. Deleting images in the Content Library or using kubectl seem like possibilities, but I'm not sure if those are the right solutions for this specific scenario.

upvoted 0 times

...

Maynard

12 months ago

This seems like a straightforward question about managing container images in an embedded Registry Service. I'll need to carefully review the options to determine the best approach.

upvoted 0 times

...

Maira

1 year ago

Option D is the way to go, no doubt. Although, I do wonder if the vSphere Client comes with a built-in 'Purge and Sanitize' button. That would be a real time-saver!

upvoted 0 times

...

Hana

1 year ago

I bet the person who wrote this question has a great sense of humor. Purging a namespace? That's like deleting your entire music library to get rid of one annoying song. But hey, it's the right answer!

upvoted 0 times

Sean

1 year ago

C) Delete the namespace using the vSphere Client.

upvoted 0 times

...

Becky

1 year ago

B) Use kubectl to delete the images.

upvoted 0 times

...

Margarett

1 year ago

A) Delete images in Content Library.

upvoted 0 times

...

...

Eric

1 year ago

Hmm, deleting images in the Content Library (option A) sounds like it might work, but I don't think that's the intended solution here. Definitely going with D.

upvoted 0 times

...

Vivan

1 year ago

Deleting the namespace using the vSphere Client (option C) seems like overkill. I'm going with D, the purge option.

upvoted 0 times

Royal

1 year ago

I prefer purging a namespace using the vSphere Client (option D) for removing unreferenced container images.

upvoted 0 times

...

Julie

1 year ago

I agree, deleting images in Content Library (option A) is also a good option.

upvoted 0 times

...

Sharika

1 year ago

I think using kubectl to delete the images (option B) is the best way to go.

upvoted 0 times

...

...

Jose

1 year ago

Option B is tempting, but using kubectl to delete the images might not be the most efficient approach. I'd go with D.

upvoted 0 times

Salome

1 year ago

Yeah, deleting the namespace using the vSphere Client could be a better option.

upvoted 0 times

...

Teddy

1 year ago

I agree, but purging a namespace using the vSphere Client might be more efficient.

upvoted 0 times

...

Blythe

1 year ago

I think using kubectl to delete the images is the way to go.

upvoted 0 times

...

...

Izetta

1 year ago

I think option D is the correct answer. Purging a namespace seems like the best way to remove unreferenced container images from the embedded Registry Service.

upvoted 0 times

Kimbery

1 year ago

Using kubectl to delete the images could also work, but purging the namespace seems more thorough.

upvoted 0 times

...

Carlota

1 year ago

I agree, deleting the namespace using the vSphere Client would clean up the images.

upvoted 0 times

...

Madonna

1 year ago

Purging a namespace seems like the best way to remove unreferenced container images from the embedded Registry Service.

upvoted 0 times

...

Tammara

1 year ago

I think option D is the correct answer.

upvoted 0 times

...

...

Carman

1 year ago

I'm not sure, but maybe purging a namespace using the vSphere Client could also work.

upvoted 0 times

...

Katina

1 year ago

I agree with Carissa, using kubectl seems like the right way to remove unreferenced container images.

upvoted 0 times

...

Carissa

1 year ago

I think we can use kubectl to delete the images.

upvoted 0 times

...