Will this command ensure that overlay traffic between service tasks is encrypted?

Will this command ensure that overlay traffic between service tasks is encrypted?

Solution: docker service create –network –encrypted
A . Yes
B . No

View Answer

Answer: B

Explanation:

= The command docker service create –network –encrypted will not ensure that overlay traffic between service tasks is encrypted. This is because the –network flag requires an argument that specifies the name or ID of the network to connect the service to1. The –encrypted flag is not a valid option for docker service create2. To encrypt overlay traffic between service tasks, you need to use the –opt encrypted flag on docker network create when you create the overlay network3.

For example:

docker network create –opt encrypted –driver overlay my-encrypted-network

Then, you can use the –network flag on docker service create to connect the service to the encrypted network. For example:

docker service create –network my-encrypted-network my-service

Reference: docker service create | Docker Documentation

docker service create | Docker Documentation

Manage swarm service networks | Docker Docs

I hope this helps you understand the command and the encryption, and how they work with Docker and swarm. If you have any other questions related to Docker, please feel free to ask me.