QCM : Mastering Docker: Container Architecture and Deployment — 9 questions

Explication

Docker Engine is the core component that runs and manages containers, handling image building, container execution, and resource allocation. The other options serve different roles: CLI is the command interface, Registry stores images, and Compose orchestrates multi-container setups.

Explication

Docker containers are designed to package applications and their dependencies in isolated environments, not to emulate full OS systems.

Explication

Resource isolation in containers, achieved through Linux namespaces and cgroups, primarily serves to prevent interference between containers and the host system, ensuring secure and predictable operation of multiple containers on a single host.

Explication

Docker Engine is the core component that handles container execution, image management, and resource allocation.

Explication

Docker images are constructed from multiple immutable layers that are stacked to form the complete filesystem. Containers are runtime instances that add a writable layer on top of these image layers, but they are not layered in the same sense. Therefore, images are layered structures, whereas containers are not layered but have a layered architecture.

Explication

Docker images are static, read-only templates used to instantiate containers, providing a consistent environment for container creation.

Explication

Docker supports bind mounts, volumes, and in-memory storage for data persistence and sharing; full disk duplication is not a storage option in Docker.

Explication

Docker supports host port mapping, bridge networks, and user-defined networks to enable container communication and external access.

Explication

A Dockerfile contains instructions to automate building Docker images, defining the environment, and setting up the application environment.