From Docker to Kubernetes: A Step-by-Step Guide to Container Orchestration Quiz

Explore key concepts in container orchestration, including core differences between Docker and Kubernetes, container management, and the transition to scalable, production-ready deployment patterns.

1. Understanding Docker's Role

   What is the primary function of Docker in modern application deployment?

   1. Orchestrating clusters of containers across multiple servers
   2. Managing cloud infrastructure security settings
   3. Monitoring network traffic for distributed systems
   4. Creating and running containers that package applications and dependencies

   Explanation: Docker is mainly used to create, manage, and run containers, allowing applications to be packaged with all necessary components. It does not orchestrate clusters (that is Kubernetes' role), nor is it responsible for cloud security or networking monitoring.

2. Kubernetes Capabilities

   Which task is Kubernetes designed to automate in large-scale container deployments?

   1. Creating individual Docker container images
   2. Compiling application code into executables
   3. Scaling and self-healing of application containers
   4. Allocating storage for virtual machines

   Explanation: Kubernetes specializes in orchestrating, scaling, and automatically recovering containers across clusters. It does not compile code, manage VM storage, or build Docker images; those tasks are handled by other tools.

3. Docker vs. Kubernetes Responsibilities

   When deploying a web application using containers across multiple servers, what distinct responsibility does Kubernetes have compared to Docker?

   1. Orchestrating and managing containers across distributed servers
   2. Building application images from source code
   3. Providing version control for container files
   4. Encrypting traffic between containers

   Explanation: Kubernetes orchestrates and manages containers across many servers, handling scaling, health checks, and networking. Docker is focused on building images and running containers, but not orchestration. Version control and encryption are handled by separate tools or features.

4. Transition Motivation

   Why might an organization move from using only Docker to incorporating Kubernetes in their container strategy?

   1. To limit the number of containers to just one per host
   2. To enable automatic scaling and load balancing of applications
   3. To run containers strictly on local developer machines
   4. To replace all microservices with a single monolithic service

   Explanation: Kubernetes provides enhanced capabilities such as scaling, load balancing, and self-healing, suitable for managing growing and complex applications. The other options either contradict scalability or do not address orchestration objectives.

5. Step-by-Step Migration

   What is a typical first step when moving an application from Docker-only deployment to Kubernetes management?

   1. Disabling container networking features
   2. Deleting all existing Docker images
   3. Writing Kubernetes YAML configuration files for deployment
   4. Converting containers into virtual machines

   Explanation: A key step is to translate how the application runs in Docker into Kubernetes YAML configuration files, which define deployments, services, and other orchestration features. The other options are incorrect and would hinder application migration.