Cyber Monday 2024! 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 PL
Mob_nav_barsMENU

Docker Exam DCA Topic 4 Question 101 Discussion

Actual exam question for Docker's DCA exam
Question #: 101
Topic #: 4
[All DCA Questions]

In Docker Trusted Registry, is this how a user can prevent an image, such as 'nginx:latest', from being overwritten by another user with push access to the repository?

Solution: Keep a backup copy of the image on another repository.

Show Suggested Answer Hide Answer
Suggested Answer: B

: = Keeping a backup copy of the image on another repository is not how a user can prevent an image, such as 'nginx:latest', from being overwritten by another user with push access to the repository. This approach does not prevent the original image from being overwritten, it only provides a way to restore it from another source. However, this may not be reliable or efficient, as the backup repository may not be in sync with the original one, or may not be accessible at all times.To prevent an image from being overwritten by another user, the user can use the DTR web UI to make the tag immutable1. This feature allows the user to lock a specific tag, so that no one can push a new image with the same tag to the repository.This ensures that the image is always consistent and secure1.Reference:

Make a tag immutable | Docker Docs


by Charlene at Sep 16, 2024, 06:36 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Paris
1 months ago
Keeping a backup? Psh, that's child's play. I just print out the image and keep it in a fireproof safe. Analog is the way to go, people!
upvoted 0 times
Kimberely
21 days ago
User 4: I prefer the digital backup method.
upvoted 0 times
...
Katina
22 days ago
User 3: Haha, that's a creative solution!
upvoted 0 times
...
Sue
24 days ago
User 2: No
upvoted 0 times
...
Elden
25 days ago
User 1: Yes
upvoted 0 times
...
...
Novella
1 months ago
Backing up your images is like making a personal insurance policy for your Docker registry. It's a no-brainer!
upvoted 0 times
...
Solange
2 months ago
Wait, so the solution is to just make a copy of the image somewhere else? That seems kinda obvious, but I guess it works.
upvoted 0 times
...
Laurel
2 months ago
Definitely, you can't be too careful when it comes to your Docker images. Backing them up is a smart move.
upvoted 0 times
...
Fanny
2 months ago
I think keeping a backup copy is a good idea, just in case someone tries to mess with the repository.
upvoted 0 times
Rodrigo
4 days ago
I agree, having a backup copy can definitely prevent any unwanted changes.
upvoted 0 times
...
Carmela
5 days ago
A) Yes
upvoted 0 times
...
Rodrigo
6 days ago
That's a good point, it's always better to be safe than sorry.
upvoted 0 times
...
Rosalyn
7 days ago
A) Yes
upvoted 0 times
...
...
Narcisa
2 months ago
Hey, at least they're not asking us to 'docker pull nginx:latest' and then 'docker rmi nginx:latest' to prevent overwrites. That would be like trying to catch a greased pig with your bare hands.
upvoted 0 times
Demetra
1 months ago
A) Yes
upvoted 0 times
...
Georgeanna
1 months ago
B) No
upvoted 0 times
...
Francoise
1 months ago
A) Yes
upvoted 0 times
...
...
Allene
2 months ago
Keeping a backup copy? Sounds like too much work. I'd rather just use a different image tag and call it a day. Less hassle, you know?
upvoted 0 times
...
Teresita
2 months ago
Wait, so they want me to just back it up somewhere else? That's like putting a lock on my front door but leaving the back door wide open. I don't think that's the best solution here.
upvoted 0 times
Dino
28 days ago
Jeannetta: That could be a more secure option to consider.
upvoted 0 times
...
Thad
1 months ago
User 3: I agree, that doesn't sound like a secure solution.
upvoted 0 times
...
Derrick
1 months ago
User 3: What about setting up permissions or access controls for the repository?
upvoted 0 times
...
Jeannetta
1 months ago
User 2: Maybe there's a better way to prevent the image from being overwritten.
upvoted 0 times
...
Una
1 months ago
User 2: No
upvoted 0 times
...
Nydia
1 months ago
User 1: I agree, that doesn't sound like a secure solution.
upvoted 0 times
...
Raina
1 months ago
Yes
upvoted 0 times
...
...
Linn
2 months ago
A) Yes, keeping a backup copy seems like a practical solution to avoid losing important images.
upvoted 0 times
...
Catrice
3 months ago
Nah, that's not gonna work. If I wanted to stop my 'nginx:latest' from getting overwritten, I'd just lock the repo down and control who has push access. Easy peasy!
upvoted 0 times
Laurene
2 months ago
No
upvoted 0 times
...
Gerald
3 months ago
Yes
upvoted 0 times
...
...
Rolland
3 months ago
B) No, I think there might be a better way to prevent image overwriting.
upvoted 0 times
...
Stephanie
3 months ago
A) Yes, that sounds like a good idea to prevent overwriting.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77