Discuss Docker DCA Exam Topic 4 Question 101

A company's security policy specifies that development and production containers must run on separate nodes in a given Swarm cluster.

Can this be used to schedule containers to meet the security policy requirements?

Solution: label contraints

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

29 comments · newest first

Willie 10 months ago

Definitely, it's a best practice for security!

Brittni 11 months ago

No way, I thought they were just for resource allocation.

Francine 11 months ago

Wait, can label constraints really do that?

Jamal 11 months ago

Totally agree, it's a solid approach.

Alberto 11 months ago

Yes, label constraints can enforce that.

Felice 12 months ago

Yes, I believe label constraints are the way to go here. We discussed this in class, and it seems to fit the security policy requirements perfectly.

Marylou 12 months ago

I'm a bit confused about how label constraints work in Swarm. Can they really enforce such strict separation?

Casey 12 months ago

I remember practicing a similar question where we had to use node labels for scheduling. I think this is the right approach!

Lynette 1 year ago

I think using label constraints could definitely help in separating the containers, but I'm not entirely sure if it's the only solution.

Chantell 1 year ago

Ah, this is a good one. I've worked with Swarm clusters before, and I know label constraints can be used to control where containers are deployed. I'm confident I can figure out the right approach for this security policy requirement.

King 1 year ago

Label constraints, huh? I'm not too familiar with that Docker feature, but it sounds like it could be the solution here. I'll need to do some quick research on how to set that up.

Sheron 1 year ago

Hmm, this looks like a tricky one. I'll need to think through the Swarm cluster setup and how label constraints can be used to schedule containers based on the security policy.

Janna 1 year ago

Okay, I think I understand the question. If we can use label constraints to schedule the containers, then the answer should be yes. Let me double-check the details on how to implement that.

Cristen 1 year ago

I'm pretty sure the answer is A. What, did you think I was going to go with B? I'm not falling for that one again.

Antonette 1 year ago

↳ replying to Cristen

I'm pretty sure the answer is A. What, did you think I was going to go with B? I'm not falling for that one again.

Lottie 1 year ago

↳ replying to Cristen

Definitely, using label constraints is the way to go to ensure containers are scheduled properly.

Tegan 1 year ago

↳ replying to Cristen

B) No

Kanisha 1 year ago

↳ replying to Cristen

I agree, it seems like the best option to meet the security policy requirements.

Delfina 1 year ago

↳ replying to Cristen

Yes

Venita 1 year ago

↳ replying to Cristen

A) Yes

Timmy 1 year ago

Yes, label constraints are the way to go. Now, if only I could find a label that says 'keep the boss away from the production server'.

Vivan 1 year ago

Label constraints? That's like using duct tape to fix a leaky faucet. It'll probably work, but it ain't pretty.

Scarlet 1 year ago

↳ replying to Vivan

Label constraints? That's like using duct tape to fix a leaky faucet. It'll probably work, but it ain't pretty.

Lonny 1 year ago

↳ replying to Vivan

B) No

Wava 1 year ago

↳ replying to Vivan

A) Yes

Teresita 1 year ago

Ah, the old 'separate nodes' conundrum. I bet the security team has been having a field day with this one.

Lashunda 1 year ago

I think the solution provided is effective in meeting the security policy requirements, so I would go with option A) Yes.

Isaiah 1 year ago

I agree with Goldie, using label constraints is a good way to ensure containers are running on separate nodes for security purposes.

Goldie 2 years ago

Yes, we can use label constraints to schedule containers on separate nodes.

Docker DCA Exam - Topic 4 Question 101 Discussion