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 12

  1. b and c: There are two labels that are always required. We will need to ensure Interlock forwards the service's requests using com.docker.lb.hosts and com.docker.lb.port. These will have all the required information, but com.docker.lb.network is recommended and required if the service's instances are attached to more than one network. We need to specify which network should be used as an ingress.
  2. b: The Interlock solution is based on a main process named interlock, a process for managing external proxy services and configurations, and an interlock-proxy service that will run inside the Docker Enterprise environment if no external load balancer is specified. These three processes run as services within Docker Swarm and they are prefixed with ucp-. ucp-interlock-controller does not exist.
  3. d: By default, only the ucp-interlock service will be located by the node's roles. All other components can run anywhere. We will use location constraints to run the ucp-interlock...