Exam Professional Cloud Architect topic 1 question 154 discussion

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

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

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.

B is answer

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

really powefull kubernetes-engine-with-kubemci

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

go for C

B is funny

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.

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.

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

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.

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

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.

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

C is correct, however, this question is an old question and need to be updated to use the ingress for global HTTPS LB