Exam Professional Cloud Architect topic 1 question 129 discussion

Answer is A

Answer is A 100% B is incorrect. Ingress comes with a HTTP(S) LB with external IP hence is not needed for communications within the cluster internally.

Deploy each service as a DEPLOYMENT, and in this case use DNS.

Correct answer is A

A is correct answer

each microservice with a specific number of replicas = Deployment internal to the cluster = Service

Benefit of using Service Leveraging service allows for you to set up your environment with static IP addresses. So when your pods die and restart the IP address associated with the deceased pod remains for the new pod that replaces it (ephemeral). I think using "Service" is helpful if you are setting up your pods to be able to communicate with specific pods in the cluster. Benefit of using DNS for Service Using DNS for your Service (static IP) you can look up Services and/or Pods by name instead of IP. Addressability by name instead of IP is easier for me.

l l Benefit of using Service Leveraging service allows for you to set up your environment with static IP addresses. So when your pods die and restart the IP address associated with the deceased pod remains for the new pod that replaces it (ephemeral). I think using "Service" is helpful if you are setting up your pods to be able to communicate with specific pods in the cluster. Benefit of using DNS for Service Using DNS for your Service (static IP) you can look up Services and/or Pods by name instead of IP. Addressability by name instead of IP is easier for me.

A is ok

A is ok

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.

I got this question in exam.

ngress comes with a HTTP(S) LB with external IP hence is not needed for communications within the cluster internally.Microservice as Deployment - used to create replicas as per this request DNS name - used as an alias service name for External name which is user for internal requests

vote A

A is right, There is no need of Ingress here because all service need to communicate internally...

Vote A 1. Based on the description "You want to be able to configure each microservice with a specific number of replicas.", It's a hint to use either Deployment or StatefulSet based on the service type is stateless or stateful, since the option only has Deployment, thus Option C and D is out. 2. Based on the description "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." the later part is the key point, which means the traffic direct to each service is based on some certain rules, in K8S this means URL, which is Ingress with external HTTP LB.

Of course it is A