Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam

Exam Professional Cloud Architect topic 1 question 154 discussion

Actual exam question from Google's Professional Cloud Architect

Question #: 154
Topic #: 1

[All Professional Cloud Architect Questions]

Your company has a stateless web API that performs scientific calculations. The web API runs on a single Google Kubernetes Engine (GKE) cluster. The cluster is currently deployed in us-central1. Your company has expanded to offer your API to customers in Asia. You want to reduce the latency for users in Asia.
What should you do?

A. Create a second GKE cluster in asia-southeast1, and expose both APIs using a Service of type LoadBalancer. Add the public IPs to the Cloud DNS zone.
B. Use a global HTTP(s) load balancer with Cloud CDN enabled.
C. Create a second GKE cluster in asia-southeast1, and use kubemci to create a global HTTP(s) load balancer.
D. Increase the memory and CPU allocated to the application in the cluster.

Show Suggested Answer

Suggested Answer: C 🗳️

by vladik820 at Aug. 25, 2021, 2:58 p.m.

Comments

Submit Cancel

vladik820

Highly Voted 3 years, 4 months ago

C is ok . https://cloud.google.com/blog/products/gcp/how-to-deploy-geographically-distributed-services-on-kubernetes-engine-with-kubemci

upvoted 37 times

rishab86

3 years, 3 months ago

After going through the link I feel its C

upvoted 3 times

mikesp

3 years, 2 months ago

Mee too. CDN does not make sense

upvoted 6 times

bandegg

1 year ago

Indeed. We don't know if the API is authenticated, reveals private data, static or not.

upvoted 1 times

...

Lk9876

Highly Voted 3 years, 4 months ago

I'm not sure about C. kubemci is deprecated and is not part anymore of cloud sdk in favor of ingress for anthos. I'll go with A

upvoted 11 times

MikeB19

3 years, 4 months ago

I think either a or c is correct. I chose c base on the article ref in the chat. Do u have supporting article ref kubemci is deprecated? I also found some chatter about kubemci being deprecated but couldn’t find anything offical

upvoted 1 times

Linus11

3 years, 3 months ago

It is hee -- https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress

upvoted 2 times

...

Rzla

3 years, 3 months ago

Problem with A is that a service load bancer is not l7 https. The question is outdated, the answer will have been C. Now it would be Anthos multi cluster ingress -https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress

upvoted 14 times

cotam

3 years, 2 months ago

That's actually not true. Service of type: LoadBalancer, is a service from "K8s" point of view, which creates L7 HTTP(S) Load Balancer.

upvoted 5 times

huuthanhdlv

7 months, 3 weeks ago

Nope, service is L4 Network/Internal load balancer

upvoted 1 times

...

dija123

9 months ago

Agree with you

upvoted 1 times

...

gcloud007

Most Recent 6 months, 2 weeks ago

Selected Answer: C

C is correct .. https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress

upvoted 1 times

...

svkds

8 months, 1 week ago

Selected Answer: B

To reduce latency for users in Asia while maintaining high availability and scalability, the most appropriate option would be: B. Use a global HTTP(s) load balancer with Cloud CDN enabled.

upvoted 3 times

...

Diwz

9 months, 2 weeks ago

Selected Answer: B

B is answer

upvoted 2 times

...

Pime13

11 months, 3 weeks ago

Selected Answer: C

question is old but it should be c. however currently should be multi cluster ingress https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress

upvoted 5 times

...

AzFarid

1 year ago

really powefull kubernetes-engine-with-kubemci

upvoted 1 times

...

theBestStudent

1 year, 1 month ago

Well it should be C, but it is deprecated in favor of ingress for Anthos as can be read here https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress

upvoted 2 times

...

tamj123

1 year, 3 months ago

go for C

upvoted 1 times

...

RaviRS

1 year, 4 months ago

Selected Answer: C

B is funny

upvoted 2 times

...

Vignesh_Krishnamurthi

1 year, 6 months ago

If it is an API performing scientific calculations then its customer base is a very specific targeted group. It should not be considered as a mass market app that is used by lots of people all over the world. Considering the business purpose of the API, option B would be more than sufficient to serve the need of customers anywhere in the world.

upvoted 1 times

...

kapara

1 year, 6 months ago

IDK if this question will be in the exam bc the answer should be C. but kubemci has now been deprecated in favor of Ingress for Anthos. Ingress for Anthos is the recommended way to deploy multi-cluster ingress.

upvoted 3 times

...

BiddlyBdoyng

1 year, 7 months ago

The problem with B is the question very much infers we are dealing with dynamic content & not static.

upvoted 1 times

...

BiddlyBdoyng

1 year, 7 months ago

It's A or C but I think A might be better. A is a simpler solution. Cloud DNS allows you to add multiple targets and part of its decision making is the latency. https://cloud.google.com/dns/docs/zones/zones-overview Tough but I think A because it's only one API being exposed. Ingress comes into its own when exposing many services.

upvoted 1 times

...

r1ck

1 year, 11 months ago

kubemci - deprecated https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress

upvoted 4 times

...

omermahgoub

2 years ago

A good option for reducing latency for users in Asia accessing the web API would be to create a second GKE cluster in asia-southeast1 and use kubemci to create a global HTTP(s) load balancer. Option C, "Create a second GKE cluster in asia-southeast1, and use kubemci to create a global HTTP(s) load balancer," would be the correct choice for this scenario. By creating a second GKE cluster in asia-southeast1, you can reduce latency for users in Asia by serving the API from a closer location. You can then use kubemci, a command-line tool that simplifies the process of creating a global HTTP(s) load balancer, to expose the APIs from both clusters through a single global IP address. This allows users to access the API with low latency, regardless of their location.

upvoted 2 times

omermahgoub

2 years ago

Option A, "Create a second GKE cluster in asia-southeast1, and expose both APIs using a Service of type LoadBalancer. Add the public IPs to the Cloud DNS zone," would not be a good choice because it would not provide a single global IP address for users to access the API, which would increase latency and complexity. Option B, "Use a global HTTP(s) load balancer with Cloud CDN enabled," would not be a good choice because it would not allow you to serve the API from a closer location for users in Asia. Option D, "Increase the memory and CPU allocated to the application in the cluster," would not be a good choice because it would not address the issue of latency for users in Asia accessing the API.

upvoted 2 times

...

ale_brd_111

2 years, 1 month ago

Selected Answer: C

Answer is C but kubemci is deprecated, now you have to go with: Multi Cluster Ingress is a cloud-hosted controller for Google Kubernetes Engine (GKE) clusters. It's a Google-hosted service that supports deploying shared load balancing resources across clusters and across regions. To deploy Multi Cluster Ingress across multiple clusters, complete Setting up Multi Cluster Ingress then see Deploying Ingress across multiple clusters. https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress

upvoted 5 times

...

Load full discussion...