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 8

  1. a: Docker Swarm is built into Docker Engine, but we have to enable Swarm mode for it to work. We can deploy other orchestrators such as Kubernetes, but it will involve extra work to deploy them. Orchestrators allow us to deploy applications on clusters, hence Swarm will deploy distributed applications.
  2. d: Docker Swarm provides service discovery via DNS, internal load balancing for services and their tasks, and overlay networking for services and containers distributed on different nodes.
  3. b: Each cluster has only one leader node. The leader is elected from the available managers. When we initialize a cluster, the first node will be the leader until a new election is required. All managers will run workloads unless we specifically avoid them using service constraints.
  4. d: Roles can be changed as we require, such as for maintenance, for example. We need to always maintain the defined number of odd managers to avoid cluster instability.
  5. a and b: By default, Docker Swarm will deploy...