New Year Sale 2026! 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

Docker DCA Exam - 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:

0/2000 characters
Submit Cancel
Gerald
3 months ago
Seems a bit risky to rely on another repo for that.
upvoted 0 times
...
Stephanie
3 months ago
Definitely a good idea to have backups!
upvoted 0 times
...
Jonelle
4 months ago
Wait, can you really just overwrite 'nginx:latest'?
upvoted 0 times
...
Providencia
4 months ago
I don't think that's enough protection.
upvoted 0 times
...
Shaun
4 months ago
That's a solid backup strategy!
upvoted 0 times
...
Irma
4 months ago
I believe the answer is No. Backing up doesn't stop someone from pushing a new image; it just saves a copy elsewhere.
upvoted 0 times
...
Truman
5 months ago
I’m a bit confused. Isn’t the point of a registry to manage images? I thought there were settings to lock down access instead of just backing up.
upvoted 0 times
...
Merilyn
5 months ago
I remember a similar question about image tagging and access control. I feel like there are better ways to manage permissions than just backing up.
upvoted 0 times
...
Fatima
5 months ago
I think keeping a backup is a good practice, but I'm not sure if it actually prevents overwriting in the original repo.
upvoted 0 times
...
Shonda
5 months ago
I'm a bit unsure about this one. Is there another way to prevent image overwriting in the Docker Trusted Registry besides keeping a backup copy? I'll need to review my notes and the course material to see if I'm missing something.
upvoted 0 times
...
Lawrence
5 months ago
Ah, I think I know the answer to this one. Storing a backup copy of the image is the way to go to prevent it from being overwritten. I'm feeling pretty confident about this.
upvoted 0 times
...
Dorethea
5 months ago
Hmm, this seems like a tricky one. I'll need to think through the Docker Trusted Registry functionality carefully to figure out the best approach.
upvoted 0 times
...
Bambi
5 months ago
Keeping a backup copy of the image on another repository sounds like a reasonable solution. I'll make sure to double-check the Docker documentation to confirm this is the correct way to prevent image overwriting.
upvoted 0 times
...
Belen
5 months ago
This question seems straightforward, I think I can handle it.
upvoted 0 times
...
Jamal
5 months ago
Downstream of a gate valve sounds familiar, especially since it can create turbulence, which is often mentioned in practice questions.
upvoted 0 times
...
Dexter
1 year 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
1 year ago
I agree, setting the image to read-only is a good idea for preventing overwriting.
upvoted 0 times
...
Ben
1 year ago
No
upvoted 0 times
...
Felix
1 year ago
Yes
upvoted 0 times
...
...
Phung
1 year ago
I agree with Rolland, having a backup copy is a good precaution.
upvoted 0 times
...
Rolland
1 year ago
But keeping a backup copy on another repository seems like a safe option.
upvoted 0 times
...
Joesph
1 year ago
No, I think there might be a better way to prevent overwriting.
upvoted 0 times
...
Theola
2 years 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
1 year ago
User2
upvoted 0 times
...
Tamera
1 year ago
User1
upvoted 0 times
...
...
Alise
2 years 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
2 years 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
2 years 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
1 year ago
I agree, setting strict access controls would be a better solution.
upvoted 0 times
...
Cyndy
1 year ago
No
upvoted 0 times
...
Viola
1 year ago
No
upvoted 0 times
...
Georgene
1 year ago
Yes
upvoted 0 times
...
Olene
2 years ago
Yes
upvoted 0 times
...
...
Rolland
2 years ago
Yes, that sounds like a good way to prevent overwriting.
upvoted 0 times
...

Save Cancel