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

Summary

This chapter covered how to deploy multi-container applications on Docker hosts. We learned that the docker-compose command does not just deploy applications, but allows us to build and share all application components. Reviewing all the components' statuses is also easier because docker-compose provides a command-line interface for retrieving all the application container's standard and error outputs. We can start and stop all the components at once. But we can go even further than this: we are also able to scale the number of instances of each component up and down. This feature depends on our application logic because the Docker daemon does not know anything about our application processes.

All application components are defined in a YAML-formatted file that can be customized using variables. We learned about the most important keys and their default values in this instance. The docker-compose file is key as it describes all the application components and its resources...