Discuss Docker DCA Exam Topic 6 Question 95

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.

AYes

BNo

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

Get Premium DCA Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

34 comments · newest first

Gerald 10 months ago

Seems a bit risky to rely on another repo for that.

Stephanie 11 months ago

Definitely a good idea to have backups!

Jonelle 11 months ago

Wait, can you really just overwrite 'nginx:latest'?

Providencia 11 months ago

I don't think that's enough protection.

Shaun 11 months ago

That's a solid backup strategy!

Irma 12 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.

Truman 12 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.

Merilyn 12 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.

Fatima 1 year ago

I think keeping a backup is a good practice, but I'm not sure if it actually prevents overwriting in the original repo.

Shonda 1 year 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.

Lawrence 1 year 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.

Dorethea 1 year 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.

Bambi 1 year 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.

Belen 1 year ago

This question seems straightforward, I think I can handle it.

Jamal 1 year ago

Downstream of a gate valve sounds familiar, especially since it can create turbulence, which is often mentioned in practice questions.

Dexter 2 years 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*

Theresia 2 years ago

↳ replying to Dexter

I agree, setting the image to read-only is a good idea for preventing overwriting.

Ben 2 years ago

↳ replying to Dexter

Felix 2 years ago

↳ replying to Dexter

Yes

Phung 2 years ago

I agree with Rolland, having a backup copy is a good precaution.

Rolland 2 years ago

But keeping a backup copy on another repository seems like a safe option.

Joesph 2 years ago

No, I think there might be a better way to prevent overwriting.

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.

Yuette 2 years ago

↳ replying to Theola

User2

Tamera 2 years ago

↳ replying to Theola

User1

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?

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!

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?

Keith 2 years ago

↳ replying to Wynell

I agree, setting strict access controls would be a better solution.

Cyndy 2 years ago

↳ replying to Wynell

Viola 2 years ago

↳ replying to Wynell

Georgene 2 years ago

↳ replying to Wynell

Yes

Olene 2 years ago

↳ replying to Wynell

Yes

Rolland 2 years ago

Yes, that sounds like a good way to prevent overwriting.

Docker DCA Exam - Topic 6 Question 95 Discussion