Questions
2 of 11
1What problem does Docker Compose solve?
2What are the top-level sections in a docker-compose.yml file, and what does each do? (Demonstrates familiarity with the file's structure.)
3What's the difference between depends_on and links?
4How do you handle environment-specific configurations (dev, staging, production)?
5What's the difference between Docker Compose and Docker Swarm?
6You need to deploy a Node.js application that uses a MongoDB database and a Redis cache. How would you set this up using Docker Compose?
7How would you manage dependencies between services to ensure correct startup order?
8How do you scale a service using Docker Compose?
9How do you handle persistent storage for databases?
10How do you manage sensitive data like passwords and API keys?
11Write a docker-compose.yml file to set up a local development environment for a full-stack application (e.g., a React frontend, a Node.js/Express API, and a PostgreSQL database).
DockerDocker
Basics
Engine
Container
Images
Hub
Dockerfile
Volumes and Storage
Compose
CI-CD
Security
Performance
Using Docker
02 / 11

What are the top-level sections in a docker-compose.yml file, and what does each do? (Demonstrates familiarity with the file's structure.)

A Compose file defines three main sections:

  1. 1

    Services: Specifies the containers to run and their runtime configuration (image, build context, ports, environment variables, volumes, depends_on, healthcheck, etc.).

  2. 2

    Volumes: Declares named persistent storage volumes that can be attached to services.

  3. 3

    Networks: Defines virtual networks for container communication, allowing services to resolve each other by name for easy internal communication