Docker Networking and Volumes

Check your understanding of how Docker manages data and networking between containers.

1. What is the default network driver used by Docker when creating a new container?
2. Which command is used to create a named Docker volume?
3. Which Docker network mode allows a container to share the host's network stack directly?
4. Which Docker volume type persists data even after the container is deleted and is managed by Docker?
5. What is the purpose of the '-p' (or '--publish') flag in the 'docker run' command?
6. Which Docker network driver is designed for communication between containers running on different Docker daemons (e.g., in a swarm cluster)?
7. Which of the following are valid Docker network types?
8. Which commands can be used to inspect details of a Docker volume?
9. Which of the following are advantages of using named volumes over bind mounts?
10. Containers on which of the following Docker network modes can communicate with each other using their container names or IP addresses without requiring explicit port mapping?
11. Docker automatically creates a named volume if it does not exist when referenced in a 'docker run' command with the '-v' flag.
12. A bind mount stores data in Docker's default storage directory (/var/lib/docker/volumes) by default.
13. Containers connected to the same bridge network can communicate using their container names as hostnames (e.g., 'ping container-name').
14. What is the default driver used for Docker volumes? (single word)
15. What is the Docker command to list all existing volumes? (format: 'docker ...')
Answered 0 of 0 — 0 correct