Book Image

Docker Certified Associate (DCA): Exam Guide

By : Francisco Javier Ramírez Urea
Book Image

Docker Certified Associate (DCA): Exam Guide

By: Francisco Javier Ramírez Urea

Overview of this book

Developers have changed their deployment artifacts from application binaries to container images, and they now need to build container-based applications as containers are part of their new development workflow. This Docker book is designed to help you learn about the management and administrative tasks of the Containers as a Service (CaaS) platform. The book starts by getting you up and running with the key concepts of containers and microservices. You'll then cover different orchestration strategies and environments, along with exploring the Docker Enterprise platform. As you advance, the book will show you how to deploy secure, production-ready, container-based applications in Docker Enterprise environments. Later, you'll delve into each Docker Enterprise component and learn all about CaaS management. Throughout the book, you'll encounter important exam-specific topics, along with sample questions and detailed answers that will help you prepare effectively for the exam. By the end of this Docker containers book, you'll have learned how to efficiently deploy and manage container-based environments in production, and you will have the skills and knowledge you need to pass the DCA exam.
Table of Contents (22 chapters)
1
Section 1 - Key Container Concepts
8
Section 2 - Container Orchestration
12
Section 3 - Docker Enterprise
17
Section 4 - Preparing for the Docker Certified Associate Exam

Chapter 4

  1. c: Each container will use its own filesystem unless we declare a shared volume for them.
  2. a, b, and c: There are different types of volumes and it is not only allowed on container creation or execution.
  1. b: Docker volumes can be removed along with their associated container using the --volumes (or -v) option. A Docker volume purge will remove all unused volumes; those not associated to any container. But Docker will never remove a bind mount volume content (a local directory mounted on a container).
  2. c: Only custom bridge networks are attachable after container creation. If we create or start a container and we want it to be connected to the default bridge network, we need to recreate it and attach it to that network on container creation.
  3. b: Using --publish-all or -P will associate a random port between 32768 and 65535 to internal container port 80. A NAT rule will automatically be created by the Docker daemon to allow this communication. You can disable the Docker daemon...