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

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

LPI Exam 701-100 Topic 2 Question 79 Discussion

Actual exam question for LPI's 701-100 exam
Question #: 79
Topic #: 2
[All 701-100 Questions]

How is a Docker container image retrieved from a Docker registry?

Show Suggested Answer Hide Answer
Suggested Answer: B

Reference https://www.ibm.com/developerworks/library/mw-1608-tost-trs/index.html


by Nieves at Sep 14, 2024, 05:59 AM

Limited Time Offer

25%

Off

Get Premium 701-100 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Florencia
3 months ago
I'm not sure, but I think it makes sense that Docker would retrieve multiple images and stack them for the container.
upvoted 0 times
...
Bronwyn
3 months ago
Wait, Docker has a registry? I thought they just pulled images straight from the internet using a complex algorithm involving cat videos and memes.
upvoted 0 times
...
Lucille
3 months ago
This question is a real head-scratcher! I'm going to have to go with C - a flat hard disk image that gets mounted. Sounds like the most straightforward solution to me.
upvoted 0 times
Oretha
2 months ago
I see your point, but I still think C is the most logical option. A flat hard disk image sounds efficient.
upvoted 0 times
...
Carey
2 months ago
Actually, I think A is the way Docker retrieves a container image. It's like a ZIP archive.
upvoted 0 times
...
Sylvia
3 months ago
I disagree, I believe D is the right choice. The registry merges all components into one file.
upvoted 0 times
...
Delisa
3 months ago
I think B is the correct answer. Multiple stacked images make sense.
upvoted 0 times
...
...
Raina
4 months ago
I agree with Viki, because Docker uses a layered approach to build container images efficiently.
upvoted 0 times
...
Chan
4 months ago
A seems like a reasonable approach, but I'm not sure if Docker actually uses a ZIP archive. I'll go with B just to be safe.
upvoted 0 times
Lewis
3 months ago
I agree, B seems like the safest option.
upvoted 0 times
...
Lucina
3 months ago
That makes sense, I'll go with B as well.
upvoted 0 times
...
Maryann
3 months ago
I think Docker retrieves multiple stacked images layered on top of each other.
upvoted 0 times
...
...
Alisha
4 months ago
D sounds like the most logical answer. The registry merges all the components into a single file that Docker can download and use.
upvoted 0 times
Lewis
3 months ago
E seems unlikely, building a container from an ISO file doesn't sound like the typical process.
upvoted 0 times
...
Stefania
3 months ago
I'm not sure, but A could be a valid option as well, with a ZIP archive being extracted into the container's root file system.
upvoted 0 times
...
Shannan
3 months ago
I think B is also a possibility, with multiple stacked images layered on top of each other.
upvoted 0 times
...
Ollie
3 months ago
I agree, D does sound like the most logical answer.
upvoted 0 times
...
...
Remona
4 months ago
I think B is the correct answer. Docker retrieves multiple images and layers them on top of each other to create the container.
upvoted 0 times
Glory
3 months ago
No, actually it's C. A flat hard disk image is downloaded and mounted as the root file system.
upvoted 0 times
...
Hillary
3 months ago
I agree, B is the correct answer. The images are layered on top of each other.
upvoted 0 times
...
...
Viki
4 months ago
I think the answer is B) Multiple stacked images are retrieved and layered on top of each other.
upvoted 0 times
...

Save Cancel