Deal of The Day! 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 1 Question 106 Discussion

Is this a way to configure the Docker engine to use a registry without a trusted TLS certificate?Solution. Set INSECURE_REGISTRY in the' /etc/docker/default' configuration file.
A) Yes
B) No

Docker DCA Exam - Topic 1 Question 106 Discussion

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

Is this a way to configure the Docker engine to use a registry without a trusted TLS certificate?

Solution. Set INSECURE_REGISTRY in the' /etc/docker/default' configuration file.

Show Suggested Answer Hide Answer
Suggested Answer: A

The provided Kubernetes NetworkPolicy YAML configuration indicates that the policy applies to pods with the label tier: backend in the default namespace1. The ingress rule allows traffic from pods with the label tier: api1. Therefore, a request issued from a pod bearing only the tier: frontend label to a pod bearing the tier: backend label will be blocked by this networkPolicy1. This is because the networkPolicy does not have a rule allowing ingress from pods with the tier: frontend label1. For more information on Kubernetes NetworkPolicies, you can refer to the Kubernetes Documentation on Network Policies.


by Lashandra at Jan 22, 2025, 02:18 AM

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
Francis
7 months ago
Yes, but only for local testing, right?
upvoted 0 times
...
Stevie
8 months ago
Wait, are we really okay with insecure registries?
upvoted 0 times
...
Alyce
8 months ago
Totally agree, it's a common workaround!
upvoted 0 times
...
Lizbeth
8 months ago
I thought that was a security risk though?
upvoted 0 times
...
Merlyn
8 months ago
That's correct, you can set INSECURE_REGISTRY.
upvoted 0 times
...
Johnathon
9 months ago
I’m pretty sure this is a valid method, but I wonder if there are any security implications we discussed in our last session.
upvoted 0 times
...
Bettina
9 months ago
I'm a bit confused. I thought there was another way to configure it, maybe through the daemon.json file instead?
upvoted 0 times
...
Melita
9 months ago
Yes, I believe setting INSECURE_REGISTRY in the '/etc/docker/default' file is correct. We practiced a similar question in class.
upvoted 0 times
...
Lenna
9 months ago
I think I remember something about configuring Docker with insecure registries, but I'm not entirely sure if it's done through that specific file.
upvoted 0 times
...
Tyra
9 months ago
Ah, I remember learning about this in class. Setting the INSECURE_REGISTRY option should do the trick. I've got a good feeling about this.
upvoted 0 times
...
Emily
9 months ago
Wait, what? I'm a bit confused about the whole TLS certificate thing. I'll need to review my notes on that.
upvoted 0 times
...
Mauricio
9 months ago
Okay, let's see. The key here is understanding how to configure the Docker engine to use a registry without a trusted TLS certificate. I think I can figure this out.
upvoted 0 times
...
Douglass
9 months ago
Hmm, I'm not totally sure about this. I'll need to think it through carefully.
upvoted 0 times
...
Margot
9 months ago
This seems pretty straightforward. I'm pretty confident I can handle this one.
upvoted 0 times
...
Joseph
1 year ago
Sure, if you want to leave the door open for all the docker daemons to come in and have a field day with your registry. What could possibly go wrong?
upvoted 0 times
Malinda
1 year ago
B) True, but it's important to weigh the risks and benefits before making that decision.
upvoted 0 times
...
Mozell
1 year ago
A) It's definitely a security risk, but sometimes it's necessary for testing or development purposes.
upvoted 0 times
...
Scarlet
1 year ago
B) No
upvoted 0 times
...
Timothy
1 year ago
A) Yes
upvoted 0 times
...
...
Tequila
1 year ago
Well, if you're running this in a controlled environment and know what you're doing, maybe. But in production? Nope, not a chance.
upvoted 0 times
Lawanda
1 year ago
Well, if you're running this in a controlled environment and know what you're doing, maybe. But in production? Nope, not a chance.
upvoted 0 times
...
Jimmie
1 year ago
B) No
upvoted 0 times
...
Lavonna
1 year ago
A) Yes
upvoted 0 times
...
...
Ryan
1 year ago
Setting INSECURE_REGISTRY? Sounds like a great way to invite the hackers to the party. No thank you!
upvoted 0 times
Edda
1 year ago
B) No
upvoted 0 times
...
Idella
1 year ago
A) Yes
upvoted 0 times
...
...
Keneth
1 year ago
Ah, the age-old question of Docker security. This is a classic case of 'Yeah, you can do it, but should you?'.
upvoted 0 times
...
Rasheeda
1 year ago
That makes sense, thanks for the clarification.
upvoted 0 times
...
Gracia
1 year ago
Yes, we can set INSECURE_REGISTRY in the configuration file.
upvoted 0 times
...
Rasheeda
1 year ago
Do you think we can configure Docker engine to use a registry without a trusted TLS certificate?
upvoted 0 times
...

Save Cancel