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

Understanding stateless and stateful containers

Portability is key in modern applications because they should run in every environment (on-premises or the cloud). Containers are prepared for these situations. We will also seek the high availability of applications in production, and containers will help us here too.

Not all applications are ready for containers by default. Processes' states and their data are difficult to manage inside containers.

In Chapter 1, Modern Infrastructures and Applications with Docker, we learned that containers are not ephemeral. They live in our hosts. Containers are created, executed, and stopped or killed, but they will remain in our host until they are deleted. We can restart a previously stopped container. But this is only true in standalone environments because all information resides under the host data path-defined directory (/var/lib/docker and C:\ProgramData\docker by default on Linux and Windows, respectively). If we move our workloads (that...