Explain container security basics: images, containers, and orchestrators.

• A. Containers are immutable; images run apps; orchestrators are not used in production.
• B. Images are dynamic runtime artifacts; containers are templates; orchestrators generate code.
• C. Images are immutable templates; containers run applications; orchestrators (e.g., Kubernetes) manage deployment, RBAC, and policies.
• D. Containers store data; images execute applications.

Answer: (C)

Images are immutable templates that define the filesystem, libraries, and configuration used to run software. When you start a container from an image, you get a running, isolated instance of that software—the container executes the application in its own confined environment. Orchestrators, such as Kubernetes, coordinate the deployment of many containers, enforce access controls (RBAC), and apply policies across the cluster to govern behavior and security.

This combination supports container security by providing a reproducible base (immutable image), safe runtime isolation (the container), and centralized governance with scalable control (the orchestrator). The description that matches this is: images are immutable templates; containers run applications; orchestrators (e.g., Kubernetes) manage deployment, RBAC, and policies. Other options mix up the roles—for example, suggesting images are dynamic artifacts or that orchestrators aren’t used in production—and don’t reflect how container ecosystems operate in practice.