Why orchestration matters in Docker - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use orchestration in container management?

Which of the following best explains why orchestration tools are important when managing multiple Docker containers?

A They provide a graphical interface to edit container files directly.

B They replace the need for Dockerfiles to build container images.

C They automate deployment, scaling, and management of containers across multiple hosts.

D They convert containers into virtual machines for better performance.

💡 Hint

Think about what happens when you have many containers running on different machines.

Orchestration tools like Kubernetes or Docker Swarm help automate tasks such as deploying containers, scaling them up or down, and managing their lifecycle across multiple servers. This is essential for handling complex applications.

💻 Command Output

intermediate

Output of Docker Swarm service scaling command

What is the output after running this command to scale a Docker Swarm service named webapp to 5 replicas?

Docker

docker service scale webapp=5

A webapp scaled to 5

B Error: service webapp not found

C 5 ot delacs ppabew

D Scaling failed: insufficient resources

💡 Hint

Consider what Docker Swarm reports when a service is successfully updated.

The command updates the number of replicas for the service and outputs a confirmation like 'webapp scaled to 5'.

🔀 Workflow

advanced

Order the steps to deploy a containerized app with orchestration

Put these steps in the correct order to deploy a containerized application using an orchestration tool like Kubernetes.

A 1,2,4,3

B 4,2,1,3

C 2,1,4,3

D 2,4,1,3

💡 Hint

Think about building the image first, then making it available, then defining and applying the deployment.

First, build the Docker image locally (2), then push it to a registry (4) so the cluster can access it. Next, write the deployment config (1), and finally apply it to the cluster (3).

❓ Troubleshoot

advanced

Troubleshooting failed container scheduling in Kubernetes

You deployed a pod but it stays in Pending state. Which reason below is the most likely cause?

A No nodes have enough resources to run the pod.

B The pod image is missing a Dockerfile.

C The pod is running but logs are not visible.

D The pod has completed successfully and exited.

💡 Hint

Pending means the pod is waiting to be scheduled on a node.

If no node has enough CPU or memory, Kubernetes cannot schedule the pod, so it remains Pending.

✅ Best Practice

expert

Best practice for managing secrets in container orchestration

Which is the best practice for handling sensitive data like passwords in a container orchestration environment?

A Store secrets in environment variables inside the container image.

B Use orchestration platform's secret management features to inject secrets at runtime.

C Hardcode secrets in application source code for easy access.

D Keep secrets in plain text files inside the container filesystem.

💡 Hint

Think about security and flexibility when managing secrets.

Using the orchestration platform's secret management allows secure storage and controlled injection of secrets without baking them into images or code.