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

Explore the essentials of container orchestration and understand how Docker and Kubernetes work together to manage modern cloud-native applications. This quiz covers core concepts from container basics to scaling and orchestration strategies.

1. Understanding Docker

   Which statement best describes a container in the context of Docker?

   1. A virtual machine that simulates a physical server's complete hardware and OS.
   2. A lightweight, standalone, executable package with everything needed to run a piece of software.
   3. A method for sharing files between different operating systems.
   4. A cloud service that manages distributed databases.

   Explanation: A container is designed to be a lightweight, executable software package that includes the app code, runtime, libraries, and dependencies needed to run an application. Virtual machines are heavier as they simulate hardware and OS, which is not what containers do. File sharing and distributed databases are not definitions of containers.

2. Role of Kubernetes

   What does Kubernetes primarily provide for applications composed of many containers?

   1. Managing application source code repositories.
   2. Scheduling hardware maintenance across servers.
   3. Container orchestration including scaling, networking, and self-healing.
   4. Only image creation and running single containers.

   Explanation: Kubernetes automates operations such as scaling, load balancing, networking, and self-healing for containerized applications. It does more than just create images or run containers, which is Docker's role. Hardware maintenance and source code management are not Kubernetes features.

3. Comparing Docker and Kubernetes

   How do Docker and Kubernetes typically interact when deploying applications?

   1. Docker builds containers, and Kubernetes orchestrates and manages them at scale.
   2. Both Docker and Kubernetes only work with virtual machines.
   3. Kubernetes creates application source code, and Docker deploys it to production.
   4. Docker handles hardware provisioning, and Kubernetes assigns IP addresses.

   Explanation: Docker is used to build and run containers, while Kubernetes manages and orchestrates these containers across servers. Kubernetes does not create source code or assign IP addresses in isolation. The platforms are not limited to virtual machines.

4. Benefits of Using Kubernetes

   Which advantage does Kubernetes provide compared to managing containers individually with Docker?

   1. Kubernetes replaces the need for containers entirely.
   2. Kubernetes can automatically restart failed containers and distribute workload across multiple nodes.
   3. Kubernetes manages only storage and has no impact on running applications.
   4. Kubernetes enables packaging applications as single containers.

   Explanation: Kubernetes excels at self-healing (restarting failed containers) and balancing workloads, which helps maintain application availability. Packaging applications as containers is a Docker feature, not Kubernetes alone. Kubernetes does not replace containers and its scope is much broader than just storage.

5. Transitioning Workflow

   What is the first step when moving from using Docker alone to adopting Kubernetes for container orchestration?

   1. Continue using Docker to containerize your application before creating Kubernetes configuration files.
   2. Skip the Docker step and only write Kubernetes YAML files.
   3. Move all source code directly into a Kubernetes cluster.
   4. Immediately convert your applications to virtual machines.

   Explanation: The transition begins by using Docker to package and test applications in containers. Only afterward are Kubernetes YAML files written to describe deployment. Moving directly to virtual machines or skipping the containerization stage are not correct. Source code is not directly moved into a Kubernetes cluster without being containerized.