Which two goals can be achieved using a Kubernetes deployment? (Choose two.)

Question

Options

• AChange the container image in a Pod
• BDefine different classes of storage
• CIncrease the number of replicas of a given Pod
• DGrant an Active Directory user access to a Kubernetes cluster
• EEnsure that only one instance of a Pod will run on every node in a Kubernetes cluster

• A
  89% (31)
• B
  3% (1)
• D
  3% (1)
• E
  6% (2)

Explanation

A Kubernetes Deployment is specifically designed to manage the desired state of Pods - two of its core capabilities are rolling out a new container image (A) via image: updates that trigger a rolling update, and scaling replicas up or down (C) via the replicas: field or kubectl scale. The other options are handled by entirely different Kubernetes primitives: B (storage classes) is managed by StorageClass objects, D (AD/RBAC access) is handled by ClusterRoleBinding + an auth provider, and E (one Pod per node) is the job of a DaemonSet, not a Deployment.

Memory tip: Think of a Deployment as a fleet manager - it controls what's running (image) and how many (replicas). Anything about storage, users, or node-level scheduling is someone else's job.

No community discussion yet for this question.