What are two goals of Kubernetes in regards to containers? (Choose two.)

Question

Options

• ATo provide middleware application-level services
• BTo automate container lifecycle management
• CTo describe the desired state for deployed containers
• DTo deploy source code and build applications

• A
  7% (3)
• B
  88% (38)
• D
  5% (2)

Explanation

Kubernetes is fundamentally a container orchestration platform, and its two core goals are automating container lifecycle management (B) - handling deployment, scaling, rolling updates, and self-healing - and declaring desired state (C) - you describe what you want (e.g., 3 replicas of a container) and Kubernetes continuously reconciles reality to match that spec.

Why the distractors are wrong:

• A is wrong because Kubernetes deliberately avoids providing middleware services like message queues or databases; it leaves application-level concerns to the apps themselves or external tools.
• D is wrong because Kubernetes works with pre-built container images - it does not compile source code or run build pipelines (that's the job of CI/CD tools like Jenkins or GitHub Actions).

Memory tip: Think of Kubernetes as a self-correcting cruise control - you set the desired speed (C: desired state) and it automatically manages the engine to maintain it (B: lifecycle automation). Source code and middleware are outside the car entirely.

No community discussion yet for this question.