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 6 Question 95 Discussion

Actual exam question for Docker's DCA exam
Question #: 95
Topic #: 6
[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 Shawna at Aug 22, 2024, 11:27 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Dexter
2 months ago
Backup, schmackup. I'd just set the image to read-only and call it a day. Who needs backups when you've got super-secure permissions, am I right? *winks*
upvoted 0 times
Theresia
2 months ago
I agree, setting the image to read-only is a good idea for preventing overwriting.
upvoted 0 times
...
Ben
2 months ago
No
upvoted 0 times
...
Felix
2 months ago
Yes
upvoted 0 times
...
...
Phung
3 months ago
I agree with Rolland, having a backup copy is a good precaution.
upvoted 0 times
...
Rolland
3 months ago
But keeping a backup copy on another repository seems like a safe option.
upvoted 0 times
...
Joesph
3 months ago
No, I think there might be a better way to prevent overwriting.
upvoted 0 times
...
Theola
3 months ago
Holding a backup image on another repo? That's like keeping a spare tire in your garage and then driving on a flat. I'd just use a different image altogether, like 'apache:latest' or something.
upvoted 0 times
Yuette
2 months ago
User2
upvoted 0 times
...
Tamera
2 months ago
User1
upvoted 0 times
...
...
Alise
3 months ago
Hey, you know what they say: 'A backup a day keeps the data loss at bay!' Seriously, though, that's a good idea. Gotta protect those precious images, am I right?
upvoted 0 times
...
Sarah
3 months ago
Backup? Ain't nobody got time for that! I'd just push the image to a different tag, like 'nginx:v1' or something. Easy peasy!
upvoted 0 times
...
Wynell
3 months ago
I'm not sure if keeping a backup on another repository is the best solution. Wouldn't it be better to set strict access controls on the image to prevent overwriting?
upvoted 0 times
Keith
2 months ago
I agree, setting strict access controls would be a better solution.
upvoted 0 times
...
Cyndy
2 months ago
No
upvoted 0 times
...
Viola
3 months ago
No
upvoted 0 times
...
Georgene
3 months ago
Yes
upvoted 0 times
...
Olene
3 months ago
Yes
upvoted 0 times
...
...
Rolland
3 months ago
Yes, that sounds like a good way 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