You are developing an application using different microservices that must remain internal to the cluster. You want the ability to configure each microservice with a specific number of replicas. You al

Question

Options

• ADeploy each microservice as a Deployment. Expose the Deployment in the cluster using a
• BDeploy each microservice as a Deployment. Expose the Deployment in the cluster using an
• CDeploy each microservice as a Pod. Expose the Pod in the cluster using a Service, and use the
• DDeploy each microservice as a Pod. Expose the Pod in the cluster using an Ingress, and use the

• A
  90% (35)
• B
  3% (1)
• C
  5% (2)
• D
  3% (1)

Explanation

A Kubernetes Deployment is the correct resource for managing a set of identical, replicated pods - the 'replicas' field directly controls how many instances run. Exposing the Deployment with a ClusterIP Service gives every microservice a stable internal DNS name and virtual IP that load-balances across all current pod replicas, regardless of how many are running. This uniform address never changes even as the Deployment scales up or down. Option B is wrong because an Ingress routes external HTTP traffic into the cluster - it is not designed for internal inter-service communication. Options C and D deploy bare Pods, which lack the self-healing and replica management capabilities of Deployments.

No community discussion yet for this question.