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

Docker DCA Exam - Topic 4 Question 117 Discussion

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

You are pulling images from a Docker Trusted Registry installation

configured to use self-signed certificates, and this error appears:

`x509: certificate signed by unknown authority.

You already downloaded the Docker Trusted Registry certificate authority

certificate from https://dtr.example.com/ca.

How do you trust it? (Select two.)

Show Suggested Answer Hide Answer
Suggested Answer: C, E

To trust a self-signed certificate from a Docker Trusted Registry (DTR), you need to place the certificate in the appropriate location on all cluster nodes and restart the Docker daemon. There are two possible locations for the certificate, depending on your OS and Docker version1:

*/etc/docker/certs.d/dtr.example.com/ca.crt: This is the preferred location for Linux systems and Docker versions 1.13 and higher. This directory is scanned by Docker for certificates and keys for each registry domain2.

*Your OS certificate path: This is the fallback location for other OSes and Docker versions. You need to find the certificate store for your OS and copy the certificate there. You also need to trust the certificate system-wide, which may require additional steps depending on your OS3.

The other options are not correct because:

*Passing '-trust-certificate ca.crt to the Docker client is not a valid option. There is no such flag for the Docker client4.

*Placing the certificate in '/etc/docker/dtr/dtr.example.com.crt' is not a valid location. The certificate should be in the /etc/docker/certs.d directory, not the /etc/docker/dtr directory1.

*Passing -- insecure-registry to the Docker client is not a recommended option. This flag disables the TLS verification for the registry, which makes the communication insecure and vulnerable to attacks.


*Use self-signed certificates | Docker Docs

*Test an insecure registry | Docker Docs

*Add TLS certificates as a trusted root authority to the host OS | Docker Docs

*docker | Docker Docs

*[Deploy a registry server | Docker Docs]

Contribute your Thoughts:

0/2000 characters
Malcom
9 hours ago
Haha, who needs security when you can just use --insecure-registry? What could go wrong?
upvoted 0 times
...
Tyisha
6 days ago
E sounds like a lot of work, I'll stick with C.
upvoted 0 times
...
Jillian
11 days ago
D? Really? That's just asking for trouble.
upvoted 0 times
...
Ligia
16 days ago
C is the way to go, easy peasy.
upvoted 0 times
...
Loren
21 days ago
A and C are the correct options.
upvoted 0 times
...
Dean
26 days ago
I vaguely recall that using the '--insecure-registry' option is a workaround, but it doesn't really solve the certificate trust issue, right?
upvoted 0 times
...
Katina
1 month ago
I’m a bit confused about whether we need to restart the Docker daemon after placing the certificate. I feel like that was mentioned in one of the study sessions.
upvoted 0 times
...
Armanda
1 month ago
I think I practiced a similar question where we had to trust a self-signed certificate, and I feel like option C sounds right for that.
upvoted 0 times
...
Armanda
1 month ago
I remember something about placing certificates in specific directories, but I'm not sure if it's the '/etc/docker/certs.d/' path or something else.
upvoted 0 times
...
Lauran
2 months ago
This is a good one. I'm pretty confident that the right approach is to add the certificate to the OS certificate path and trust it system-wide, as described in option E. That's the most robust and secure solution.
upvoted 0 times
...
Felicitas
2 months ago
I'm not sure about passing the --insecure-registry flag. That seems a bit sketchy to me. I think we want to properly trust the certificate instead of just disabling the security check.
upvoted 0 times
...
Dexter
2 months ago
Okay, I've got this. We need to add the certificate to the Docker configuration on all the cluster nodes. Option C looks like the right way to do that. Easy peasy!
upvoted 0 times
...
Ernestine
2 months ago
You need to place the cert in /etc/docker/certs.d/ for it to work.
upvoted 0 times
...
Vivan
3 months ago
I feel the same! B is definitely needed to restart the daemon.
upvoted 0 times
...
Terina
3 months ago
I think D is misleading. It’s not a secure solution.
upvoted 0 times
...
Roslyn
3 months ago
Hmm, this is tricky. I'm a bit confused about the difference between the Docker client and the Docker daemon. I'll need to think this through carefully.
upvoted 0 times
...
Truman
3 months ago
I think the key here is to trust the certificate authority certificate that we've already downloaded. Looks like options B and C are the way to go, but I'm not sure which one is better.
upvoted 0 times
Jeannine
2 months ago
B and C both seem valid.
upvoted 0 times
...
Lilli
2 months ago
I agree, trusting the CA certificate is crucial.
upvoted 0 times
...
...

Save Cancel