FILL BLANK Fill in the blank to complete the statement. A user wants a Kubernetes deployment to run three separate pods of a web application at one time. In the deployment YAML, the user must configur

Question

Explanation

To run a specific number of pod instances in Kubernetes, the 'replicas' field in the 'spec' subsection of a Deployment manifest controls how many identical pod copies the ReplicaSet maintains.

Approach. The correct answer is: configure the 'replicas' field in the 'spec' subsection. Setting 'spec.replicas: 3' tells the Deployment controller to maintain exactly three running instances of the pod template at all times. If a pod crashes or is deleted, the ReplicaSet controller will automatically spin up a replacement to restore the desired count. This is the foundational mechanism for horizontal scaling and high availability in Kubernetes.

Concept tested. Kubernetes Deployment manifest structure - specifically how 'spec.replicas' controls the desired pod count managed by the underlying ReplicaSet. This tests understanding that scaling is declarative (you declare desired state) rather than imperative, and that 'spec' is the top-level subsection housing runtime configuration like replicas, selector, and the pod template.

Reference. Kubernetes Docs: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#creating-a-deployment - see the 'spec.replicas' field description

No community discussion yet for this question.