exam questions

Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam

Exam Professional Cloud Architect topic 1 question 129 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 129
Topic #: 1
[All Professional Cloud Architect Questions]

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?

  • 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.
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
MamthaSJ
Highly Voted 3 years, 2 months ago
Answer is A
upvoted 29 times
...
PeppaPig
Highly Voted 3 years, 1 month ago
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.
upvoted 19 times
...
plumbig11
Most Recent 2 months, 3 weeks ago
Selected Answer: A
Deploy each service as a DEPLOYMENT, and in this case use DNS.
upvoted 1 times
...
AWS_Sam
9 months ago
Correct answer is A
upvoted 1 times
...
heretolearnazure
1 year, 1 month ago
A is correct answer
upvoted 1 times
...
wooloo
1 year, 2 months ago
each microservice with a specific number of replicas = Deployment internal to the cluster = Service
upvoted 8 times
...
[Removed]
1 year, 8 months ago
Selected Answer: A
answer is A
upvoted 2 times
...
jay9114
1 year, 9 months ago
Selected Answer: A
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.
upvoted 9 times
...
jay9114
1 year, 9 months ago
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.
upvoted 3 times
...
Sreenivasa739
1 year, 9 months ago
A is ok
upvoted 1 times
...
megumin
1 year, 10 months ago
Selected Answer: A
A is ok
upvoted 1 times
...
minmin2020
1 year, 11 months ago
Selected Answer: A
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.
upvoted 1 times
...
ACE_ASPIRE
2 years, 1 month ago
I got this question in exam.
upvoted 4 times
Sur_Nikki
1 year, 4 months ago
I have received this sentence from u in every comment posted by u
upvoted 2 times
...
...
DrishaS4
2 years, 1 month ago
Selected Answer: A
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
upvoted 3 times
...
backhand
2 years, 2 months ago
vote A
upvoted 1 times
...
AzureDP900
2 years, 2 months ago
A is right, There is no need of Ingress here because all service need to communicate internally...
upvoted 1 times
...
JoeyCASD
2 years, 4 months ago
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.
upvoted 8 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago