Why advanced Compose features matter in Docker - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start services defined in a Compose file.

Docker

docker-compose [1]

Drag options to blanks, or click blank then click option'

Astop

Bbuild

Crm

Dup

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'build' instead of 'up' starts only the build process, not the containers.

Using 'stop' or 'rm' stops or removes containers, not starts them.

The docker-compose up command starts all services defined in the Compose file.

2fill in blank

medium

Complete the code to run Compose in detached mode (in the background).

Docker

docker-compose up [1]

Drag options to blanks, or click blank then click option'

A-d

B--force-recreate

C--remove-orphans

D--build

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--build' only rebuilds images but does not detach.

Using '--force-recreate' recreates containers but does not detach.

The -d flag runs containers in detached mode, so the terminal is free after starting.

3fill in blank

hard

Fix the error in the Compose command to remove stopped containers.

Docker

docker-compose [1]

Drag options to blanks, or click blank then click option'

Arm

Bdown

Cstop

Drestart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'down' removes containers and networks but is more destructive.

Using 'stop' only stops containers but does not remove them.

The docker-compose rm command removes stopped service containers.

4fill in blank

hard

Fill both blanks to specify a Compose file and project name.

Docker

docker-compose [1] docker-compose.yml [2] myproject up

Drag options to blanks, or click blank then click option'

A-f

B-p

C--file

D--project-name

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--file' and '--project-name' works but is longer; here short flags are expected.

Mixing flags or missing one causes errors.

The -f flag specifies the Compose file, and -p sets the project name.

5fill in blank

hard

Fill all three blanks to create a service with environment variables and restart policy.

Docker

services:
  web:
    image: nginx
    environment:
      - [1]=production
    restart: [2]
    ports:
      - "80:80"
    deploy:
      replicas: [3]

Drag options to blanks, or click blank then click option'

AENV

Balways

C3

DMODE

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'MODE' instead of 'ENV' for environment variable key.

Using '3' as restart policy instead of number of replicas.

ENV=production sets an environment variable, restart: always ensures the container restarts on failure, and replicas: 3 runs three instances.

Practice

1. What is the main benefit of using advanced features in Docker Compose for multi-container applications?

easy

A. They reduce the size of container images.

B. They make containers run faster individually.

C. They simplify managing multiple containers together.

D. They automatically update Docker itself.

Solution

1. Step 1: Understand Docker Compose purpose

   Docker Compose is designed to manage multiple containers as one app.

2. Step 2: Identify advanced features role

   Advanced features help organize, scale, and control these containers easily.

3. Final Answer:

   They simplify managing multiple containers together. -> Option C

4. Quick Check:

   Advanced Compose features = Simplify multi-container management [OK]

Hint: Think: Compose = managing many containers easily [OK]

Common Mistakes:

• Confusing image size with Compose features
• Thinking Compose speeds up single containers
• Assuming Compose updates Docker engine

2. Which of the following is the correct syntax to scale a service named web to 3 instances using Docker Compose CLI?

easy

A. docker-compose scale web 3

B. docker-compose start web -n 3

C. docker-compose run --scale web 3

D. docker-compose up --scale web=3

Solution

1. Step 1: Recall Docker Compose scale syntax

   The correct command to scale is: docker-compose up --scale servicename=number

2. Step 2: Match options with correct syntax

   docker-compose up --scale web=3 matches this syntax exactly.

3. Final Answer:

   docker-compose up --scale web=3 -> Option D

4. Quick Check:

   Scaling uses 'up --scale' syntax [OK]

Hint: Use 'docker-compose up --scale service=num' to scale [OK]

Common Mistakes:

• Using 'scale' as a separate command
• Confusing 'run' with 'up' for scaling
• Using 'start' which doesn't support scaling

3. Given this snippet in a docker-compose.yml file:

services:
  app:
    image: myapp
    deploy:
      replicas: 2
      resources:
        limits:
          cpus: '0.5'
          memory: 512M

What will happen when you run docker stack deploy -c docker-compose.yml mystack?

medium

A. The command fails because deploy is not supported in Compose.

B. Two app containers start with CPU limited to 0.5 and 512MB memory each.

C. Only one app container starts ignoring resource limits.

D. Two app containers start but without any resource limits.

Solution

1. Step 1: Understand 'deploy' in Compose for Swarm

   The 'deploy' section is used by Docker Swarm to set replicas and resource limits.

2. Step 2: Analyze command effect

   Running 'docker stack deploy' uses Swarm mode, so it respects 'replicas' and 'resources' limits.

3. Final Answer:

   Two app containers start with CPU limited to 0.5 and 512MB memory each. -> Option B

4. Quick Check:

   'deploy' works with 'docker stack deploy' = resource limits applied [OK]

Hint: Use 'docker stack deploy' to apply 'deploy' settings [OK]

Common Mistakes:

• Thinking 'deploy' works with 'docker-compose up'
• Assuming only one container starts despite replicas
• Believing resource limits are ignored in Swarm

4. You wrote this docker-compose.yml snippet:

services:
  db:
    image: postgres
    environment:
      POSTGRES_PASSWORD: mypass
    ports:
      - "5432:5432"
    deploy:
      replicas: 2

When running docker-compose up, only one db container starts. Why?

medium

A. The 'deploy' section is ignored by 'docker-compose up'.

B. You must specify replicas in 'docker-compose up' command.

C. Postgres image does not support multiple replicas.

D. Port mapping conflicts prevent multiple containers.

Solution

1. Step 1: Understand 'deploy' section scope

   The 'deploy' key is only used by Docker Swarm, not by 'docker-compose up'.

2. Step 2: Explain why only one container starts

   'docker-compose up' ignores 'deploy', so it starts one container by default.

3. Final Answer:

   The 'deploy' section is ignored by 'docker-compose up'. -> Option A

4. Quick Check:

   'deploy' ignored by 'docker-compose up' = one container [OK]

Hint: 'deploy' works only with Swarm, not 'docker-compose up' [OK]

Common Mistakes:

• Thinking 'docker-compose up' can scale with 'deploy'
• Assuming port conflicts cause single container
• Believing image limits replicas

5. You want to deploy a web app with a database using Docker Compose. You need to:
- Scale the web service to 4 instances
- Limit each web container to 1 CPU and 1GB RAM
- Ensure the database runs only once with persistent storage

Which Compose features help you achieve this setup?

hard

A. Use 'deploy.replicas' and 'deploy.resources.limits' for web; use volumes for DB persistence.

B. Use 'scale' in 'docker-compose up' for DB; use 'deploy' for web resource limits.

C. Use environment variables to limit CPU and RAM; scale DB with 'deploy.replicas'.

D. Use 'depends_on' to scale web; use 'ports' to limit DB resources.

Solution

1. Step 1: Identify scaling and resource control for web

   Use 'deploy.replicas' to scale web to 4 and 'deploy.resources.limits' to limit CPU and RAM.

2. Step 2: Ensure single DB instance with persistence

   Set DB replicas to 1 and use volumes to keep data persistent.

3. Final Answer:

   Use 'deploy.replicas' and 'deploy.resources.limits' for web; use volumes for DB persistence. -> Option A

4. Quick Check:

   Scaling + resource limits + volumes = Use 'deploy.replicas' and 'deploy.resources.limits' for web; use volumes for DB persistence. [OK]

Hint: 'deploy' controls scale and limits; volumes keep DB data safe [OK]

Common Mistakes:

• Trying to scale DB instead of web
• Using environment variables for resource limits
• Confusing 'depends_on' with scaling or resource control