Annie, a cloud security engineer, uses the Docker architecture to employ a client/server model in the application she is working on. She utilizes a component that can process API requests and handle…

Question

Options

• ADocker client
• BDocker objects
• CDocker daemon
• DDocker registries

• A
  2% (1)
• C
  96% (43)
• D
  2% (1)

Explanation

Docker Daemon Explanation

Option C is correct because the Docker daemon (dockerd) is the core background service that listens for and processes Docker API requests, while also managing Docker objects such as containers, images, volumes, and networks - exactly matching the scenario described. The Docker daemon is the "server" side of Docker's client/server architecture, doing the heavy lifting of building, running, and managing containers.

Why the distractors are wrong:

• A (Docker client): The Docker client (CLI) is what sends API requests to the daemon - it's the "client" side that users interact with, not the component that processes them.
• B (Docker objects): Docker objects (containers, images, volumes, networks) are the resources being managed, not an architectural processing component.
• D (Docker registries): Registries (like Docker Hub) are storage locations for Docker images, not request-processing components.

Memory Tip: Think of the Docker daemon as a restaurant kitchen - the Docker client is the waiter taking your order (request), but the daemon is the kitchen that actually processes and fulfills that order, managing all the ingredients (objects) needed to do so.

No community discussion yet for this question.