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

Submit Cancel
Joseph
1 months 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
9 days ago
B) True, but it's important to weigh the risks and benefits before making that decision.
upvoted 0 times
...
Mozell
13 days ago
A) It's definitely a security risk, but sometimes it's necessary for testing or development purposes.
upvoted 0 times
...
Scarlet
16 days ago
B) No
upvoted 0 times
...
Timothy
26 days ago
A) Yes
upvoted 0 times
...
...
Tequila
1 months 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
21 days 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
23 days ago
B) No
upvoted 0 times
...
Lavonna
27 days ago
A) Yes
upvoted 0 times
...
...
Ryan
2 months ago
Setting INSECURE_REGISTRY? Sounds like a great way to invite the hackers to the party. No thank you!
upvoted 0 times
Edda
9 days ago
B) No
upvoted 0 times
...
Idella
11 days ago
A) Yes
upvoted 0 times
...
...
Keneth
2 months 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
2 months ago
That makes sense, thanks for the clarification.
upvoted 0 times
...
Gracia
2 months ago
Yes, we can set INSECURE_REGISTRY in the configuration file.
upvoted 0 times
...
Rasheeda
2 months ago
Do you think we can configure Docker engine to use a registry without a trusted TLS certificate?
upvoted 0 times
...

Save Cancel