Why orchestration matters in Docker - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a Docker container named 'webapp'.

Docker

docker run --name [1] -d nginx

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

Abackend

Bdatabase

Ccache

Dwebapp

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong container name that does not match the app.

The --name option sets the container's name. Here, 'webapp' is the correct name to start the container.

2fill in blank

medium

Complete the command to list all running Docker containers.

Docker

docker [1]

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

Aps

Bimages

Crun

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'docker images' which lists images, not containers.

The docker ps command lists all running containers.

3fill in blank

hard

Fix the error in the Docker Compose file to define a service named 'app'.

Docker

services:
  [1]:
    image: nginx
    ports:
      - "80:80"

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

Abackend

Bcache

Capp

Ddatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong service name that does not match the app.

The service name should be 'app' as required. This identifies the container in orchestration.

4fill in blank

hard

Fill both blanks to create a Docker Compose service that restarts automatically on failure.

Docker

services:
  web:
    image: nginx
    restart: [1]
    ports:
      - "[2]:80"

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

Aon-failure

Balways

C8080

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'always' restart policy when only 'on-failure' is requested.

Swapping port numbers incorrectly.

The restart: on-failure option restarts the container only if it fails. Port mapping 8080:80 exposes port 80 inside the container to port 8080 on the host.

5fill in blank

hard

Fill all three blanks to define a Docker Compose service with environment variables and volume mapping.

Docker

services:
  db:
    image: postgres
    environment:
      - POSTGRES_USER=[1]
      - POSTGRES_PASSWORD=[2]
    volumes:
      - [3]:/var/lib/postgresql/data

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

Aadmin

Bsecret123

C./dbdata

D/data

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect environment variable names.

Swapping volume paths.

Environment variables set the database user and password. Volume mapping ./dbdata:/var/lib/postgresql/data stores data on the host for persistence.

Practice

1. Why is orchestration important when managing many Docker containers?

easy

A. It automates container management and keeps apps running smoothly

B. It replaces Docker images with virtual machines

C. It only helps with building Docker images

D. It slows down container startup times

Solution

1. Step 1: Understand orchestration role

   Orchestration automates tasks like starting, stopping, and monitoring many containers.

2. Step 2: Identify orchestration benefits

   It ensures apps stay running and can recover from failures automatically.

3. Final Answer:

   It automates container management and keeps apps running smoothly -> Option A

4. Quick Check:

   Orchestration = automation and reliability [OK]

Hint: Orchestration = automatic container management and health [OK]

Common Mistakes:

• Thinking orchestration replaces Docker images
• Confusing orchestration with image building
• Believing orchestration slows down containers

2. Which of the following is the correct command to deploy a Docker service with orchestration using Docker Swarm?

easy

A. docker service create --name myservice nginx

B. docker run --name myservice nginx

C. docker build -t myservice nginx

D. docker-compose up -d

Solution

1. Step 1: Identify orchestration command

   Docker Swarm uses docker service create to deploy services with orchestration.

2. Step 2: Compare other commands

   docker run runs a single container, docker build builds images, and docker-compose up is for Compose, not Swarm service creation.

3. Final Answer:

   docker service create --name myservice nginx -> Option A

4. Quick Check:

   Swarm deploy = docker service create [OK]

Hint: Swarm deploy uses 'docker service create' command [OK]

Common Mistakes:

• Using 'docker run' for orchestration
• Confusing build commands with deploy
• Mixing Docker Compose with Swarm commands

3. Given a Docker Swarm cluster with 3 nodes, what happens if you deploy a service with 5 replicas?

medium

A. Only 3 replicas run because there are 3 nodes

B. The service fails to deploy due to insufficient nodes

C. 5 replicas run distributed across the 3 nodes

D. All replicas run on a single node

Solution

1. Step 1: Understand replica distribution

   Docker Swarm schedules replicas across available nodes to balance load.

2. Step 2: Check replica count vs nodes

   Even if replicas exceed nodes, Swarm runs all replicas by placing multiple on some nodes.

3. Final Answer:

   5 replicas run distributed across the 3 nodes -> Option C

4. Quick Check:

   Replicas > nodes means multiple per node [OK]

Hint: Replicas can exceed nodes; Swarm balances them [OK]

Common Mistakes:

• Assuming replicas limited by node count
• Thinking deployment fails if replicas > nodes
• Believing all replicas run on one node

4. You tried to update a Docker service but the new containers never start. What is a likely cause related to orchestration?

medium

A. Docker daemon is not installed

B. The update command syntax was incorrect

C. Docker Compose file is missing

D. The new image tag does not exist or is invalid

Solution

1. Step 1: Analyze update failure

   If new containers fail to start after update, a common cause is the image tag is missing or wrong.

2. Step 2: Eliminate other options

   Incorrect update syntax usually causes command errors, not silent failures. Missing Compose file or Docker daemon would prevent any service management.

3. Final Answer:

   The new image tag does not exist or is invalid -> Option D

4. Quick Check:

   Invalid image tag stops new containers [OK]

Hint: Check image tag validity if update containers fail [OK]

Common Mistakes:

• Assuming syntax error without checking logs
• Ignoring image tag correctness
• Confusing Compose file with Swarm service update

5. You want to update a running Docker service with zero downtime. Which orchestration feature helps achieve this?

hard

A. Manually stopping all containers before update

B. Rolling updates that replace containers gradually

C. Rebuilding images without redeploying

D. Using a single container without replicas

Solution

1. Step 1: Understand zero downtime update

   Zero downtime means the app stays available while updating containers.

2. Step 2: Identify orchestration feature

   Rolling updates replace containers one by one, keeping service live during update.

3. Step 3: Eliminate wrong options

   Stopping all containers causes downtime, rebuilding images alone doesn't update running service, and single container lacks redundancy.

4. Final Answer:

   Rolling updates that replace containers gradually -> Option B

5. Quick Check:

   Rolling updates = zero downtime updates [OK]

Hint: Use rolling updates for zero downtime service changes [OK]

Common Mistakes:

• Stopping all containers causes downtime
• Thinking image rebuild updates running service
• Using single container lacks high availability