Google Cloud Professional Cloud Architect — Question 147

You are developing an application using different microservices that should remain internal to the cluster. You want to be able to configure each microservice with a specific number of replicas. You also want to be able to address a specific microservice from any other microservice in a uniform way, regardless of the number of replicas the microservice scales to. You need to implement this solution on Google Kubernetes Engine. What should you do?

Answer options

• 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 name to address the Pod from other microservices within the cluster.

Correct answer: A

Explanation

Option A is correct because deploying each microservice as a Deployment and exposing it via a Service allows for load balancing and consistent DNS naming, making it easy to address the service regardless of how many replicas are running. Option B is incorrect because Ingress is typically used for external access, not for internal service-to-service communication. Options C and D are wrong as they suggest deploying microservices as Pods, which do not provide the same scalability and management features as Deployments.