🌍 DevOps · flashcards

DevOps Containerization Flashcards

50 question-and-answer cards covering Containerization as it is examined in DevOps. 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

50Cards in deck
24Free preview
10Syllabus topics
~151Chars per answer
FreePrice

24 sample cards from the Containerization deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. What is a multi-stage build and why is it used?

    A Dockerfile with multiple FROM stages where build artifacts are produced in one stage and copied into a slim final stage, yielding smaller, more secure production images without build tools.

  2. What is Docker Compose?

    A tool for defining and running multi-container Docker applications using a single declarative YAML file (compose.yaml / docker-compose.yml).

  3. Which command starts all services defined in a Compose file in the background?

    docker compose up -d (the -d runs detached).

  4. What does 'docker compose down' do?

    It stops and removes the containers, default network, and (optionally with --volumes) the volumes created by 'compose up'.

  5. In a Compose file, what is the purpose of the 'depends_on' key?

    It controls the start-up and shutdown order of services, ensuring one service starts after the services it lists (note: it waits for start, not for readiness).

  6. What is Kubernetes?

    An open-source container orchestration platform that automates the deployment, scaling, healing, and management of containerized applications across a cluster of machines.

  7. What are the common tools for installing a local single-node Kubernetes cluster?

    Minikube, kind (Kubernetes in Docker), k3s, or Docker Desktop's built-in Kubernetes; kubeadm is used for bootstrapping production-style clusters.

  8. What is kubectl?

    The Kubernetes command-line client used to communicate with the cluster's API server to create, inspect, and manage resources.

  9. What are the two main parts of Kubernetes cluster architecture?

    The control plane (master components that manage the cluster) and the worker nodes (which run the application workloads).

  10. Name the four core control plane components and their roles.

    kube-apiserver (front-end/API), etcd (key-value store for cluster state), kube-scheduler (assigns Pods to nodes), and kube-controller-manager (runs controllers that reconcile desired state).

  11. What is etcd in Kubernetes?

    A consistent, distributed key-value store that holds all cluster data and configuration, acting as the single source of truth for cluster state.

  12. Name the key components that run on every Kubernetes worker node.

    kubelet (agent that manages Pods/containers), kube-proxy (handles networking/Service routing), and a container runtime (e.g., containerd).

  13. What is the role of the kube-scheduler?

    It watches for newly created Pods with no assigned node and selects an appropriate node for them based on resource requirements, constraints, and policies.

  14. What is a Pod in Kubernetes?

    The smallest deployable unit; one or more tightly coupled containers that share the same network namespace (IP), storage volumes, and are scheduled together on one node.

  15. Why are Pods considered ephemeral?

    Pods are disposable: if one dies it is not resurrected but replaced by a new Pod (with a new IP) by its controller, so workloads should not depend on a specific Pod identity.

  16. What is a Kubernetes Service and what problem does it solve?

    A Service is a stable abstraction that exposes a logical set of Pods (selected by labels) under a single, persistent IP/DNS name, providing load balancing despite Pods being ephemeral.

  17. Compare the ClusterIP, NodePort, and LoadBalancer Service types.

    ClusterIP exposes the Service only inside the cluster (default); NodePort exposes it on a static port on every node's IP; LoadBalancer provisions an external cloud load balancer to route traffic in.

  18. What is a Deployment in Kubernetes?

    A controller that manages a ReplicaSet to maintain a desired number of identical Pods, providing declarative updates, rolling updates, and rollbacks for stateless applications.

  19. What is the relationship between a Deployment, a ReplicaSet, and Pods?

    A Deployment manages ReplicaSets, and each ReplicaSet ensures the specified number of Pod replicas are running; updating a Deployment creates a new ReplicaSet.

  20. How do you scale a Deployment named web to 5 replicas using kubectl?

    kubectl scale deployment web --replicas=5 (or edit the spec.replicas field in the manifest).

  21. What is a rolling update in a Kubernetes Deployment?

    A strategy that incrementally replaces old Pods with new ones (respecting maxSurge and maxUnavailable) so the application is updated with zero downtime.

  22. What is Helm?

    A package manager for Kubernetes that lets you define, install, and upgrade applications using reusable, versioned packages called charts.

  23. What is a Helm chart, and what is a 'release'?

    A chart is a packaged collection of templated Kubernetes manifests plus default values; a release is a specific installed instance of a chart running in a cluster.

  24. What is the purpose of the values.yaml file in a Helm chart?

    It supplies the default configuration values that are injected into the chart's templates, allowing customization at install/upgrade time without editing the templates.

What this deck covers

The Containerization deck follows the DevOps Containerization syllabus — 3 chapters and 10 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 16.7 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 151 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Containerization flashcards FAQ

How many Containerization flashcards are in this DevOps deck?

50 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these DevOps flashcards free?

Yes. The preview here is free to read with no signup, and the full 50-card deck is free inside the Examius app.

What do the Containerization cards cover?

They follow the DevOps Containerization syllabus — 3 chapters and 10 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.