Answer-first summary for fast verification
Answer: Deploy each microservice as a Deployment. Expose the Deployment in the cluster using a Service, and use the Service DNS name to address it from other microservices within the cluster.
To meet the requirements, each microservice should be deployed as a Deployment to manage replicas. Exposing the Deployment via a Service provides a stable DNS name for internal communication. Services handle load balancing across replicas, ensuring uniform addressing. Ingress (options B/D) is for external access, which isn't needed here. Deploying as Pods (C/D) lacks scalability. Thus, option A is correct.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
How can you implement a solution on Google Kubernetes Engine where internal microservices can be configured with specific replica counts while maintaining uniform addressing between services, regardless of scaling?
A
Deploy each microservice as a Deployment. Expose the Deployment in the cluster using a Service, and use the Service DNS name to address it from other microservices within the cluster.
B
Deploy each microservice as a Deployment. Expose the Deployment in the cluster using an Ingress, and use the Ingress IP address to address the Deployment from other microservices within the cluster.
C
Deploy each microservice as a Pod. Expose the Pod in the cluster using a Service, and use the Service DNS name to address the microservice from other microservices within the cluster.
D
Deploy each microservice as a Pod. Expose the Pod in the cluster using an Ingress, and use the Ingress IP address to address the Pod from other microservices within the cluster.
No comments yet.