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

Explore the transition from containerization to orchestration, learning core differences and practical concepts from Docker to Kubernetes. Ideal for those seeking foundational understanding in modern DevOps workflows.

1. Understanding Docker's Role

   Which statement best describes what Docker is used for in application deployment?

   1. Orchestrating hundreds of containers across different servers
   2. Packaging and running a single application or microservice in a container
   3. Running only virtual machines, not containers
   4. Replacing all cluster management tools

   Explanation: Docker is primarily designed to package, run, and manage single applications or microservices inside lightweight containers. Orchestrating containers across servers is the job of orchestration tools like Kubernetes, not Docker. Docker does not replace all cluster management tools, and it specifically deals with containers, not virtual machines.

2. Purpose of Kubernetes

   What is the main purpose of Kubernetes in container management?

   1. Providing database solutions for web apps
   2. Creating basic isolated runtime environments
   3. Building container images from application code
   4. Managing complex applications by automating container deployment and scaling

   Explanation: Kubernetes is designed to orchestrate complex applications by automating the deployment, scaling, load balancing, and management of containers. It does not build container images (that is typically Docker's role) or serve as a database solution, and while it creates isolated environments, its primary value is orchestration, not individual runtime creation.

3. Docker and Kubernetes Relationship

   How do Docker and Kubernetes typically complement each other in containerized workflows?

   1. Docker creates and manages containers, while Kubernetes orchestrates them across multiple servers
   2. Kubernetes builds application code into container images
   3. Docker is responsible for load balancing between containers
   4. Both only run individual containers without scaling abilities

   Explanation: Docker is responsible for creating and running containers, and Kubernetes takes those containers to manage them at scale, across clusters and nodes. Kubernetes does not build container images, and Docker alone does not manage load balancing across clusters, nor do both lack scaling abilities when combined.

4. Benefits of Moving to Orchestration

   Which of the following is a primary benefit of using Kubernetes instead of only Docker for deployment?

   1. Automatic recovery and redistribution of containers after failures
   2. Eliminating the need for container images
   3. Faster application code compilation
   4. Better support for legacy monolithic applications

   Explanation: Kubernetes provides self-healing by restarting failed containers and redistributing them if needed, making deployments more resilient. It does not handle code compilation, is not specifically aimed at legacy monolithic apps, and container images remain necessary.

5. Transition Process from Docker to Kubernetes

   After creating a working Docker container for an app, what is the typical next step to deploy it with Kubernetes?

   1. Convert the container to a virtual machine image
   2. Write a Kubernetes YAML file to define deployment settings
   3. Publish source code directly to a registry with no configuration
   4. Install additional operating systems inside the container

   Explanation: The next step is to write a Kubernetes YAML configuration file, which defines how the application is deployed, scaled, and managed by Kubernetes. Installing operating systems or converting to virtual machines is unnecessary, and Kubernetes requires configuration, not just source code publishing.