Exam Professional Cloud Architect topic 7 question 4 discussion

IMHO d) is the correct answer, not a) The game fulfills the business requirements as well as the technical requirements - so it is build upon an architecture that is multi regional. https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress

D for me. since it's a multiple regions game.Need multi-GKE or multi-MIG. To configure the ingress between multi-GKE. kubemci or Ahthos kubemci has now been deprecated in favor of Ingress for Anthos. Ingress for Anthos is the recommended way to deploy multi-cluster ingress. https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress So. D

According to the scenario they are not using GKE for now, they only plan to use it. They moved from on-premises VM almost without modification. So answer A is also plausible

Isn't kubemci the equivalent of a multi-cluster ingress?? What's the difference here between D and B?

There is no need for Anthos as Mountkrik has migrated all of its games to Google Cloud. Anthos should be used in a hybrid environment scenario.

why not the other options? A. Managed Instance Group with Compute Engine: While this can achieve regional deployments, it wouldn't offer containerization benefits like GKE. GKE provides features like autoscaling and health checks, which are well-suited for managing game workloads. B. Kubemci with Global Load Balancer: Kubemci is a tool for managing on-premise Kubernetes clusters, not directly applicable to Google Cloud's GKE. D. Ingress for Anthos: Anthos is a suite of tools for managing hybrid and multi-cloud deployments. While it can integrate with GKE and global load balancers, it's a more complex solution compared to simply using a global load balancer with GKE for this specific scenario.

GKE + global rb = Ingless for Anthos.

I had a test today. kubemci and Ingress for Anthos were deprecated . Ingress for Anthos was replaced with "Multi Cluster Ingress" in the actual test.

Well, here B is the deprecated right answer, but nowadays D is the current right answer.

D As per the below documentation, the best option found is D: https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress

B is the answer: B. Configure kubemci with a global load balancer and Google Kubernetes Engine (GKE). This approach provides a scalable, highly available, and manageable solution for routing traffic to regional game instances deployed across multiple Google Cloud regions. Kubemci is a multi-cluster Ingress controller that enables managing Ingress resources across multiple GKE clusters, making it ideal for handling regional game instances. A global load balancer distributes incoming traffic across multiple regions, ensuring that users are directed to the nearest and most responsive game instance.

Adding an article explaining why D could be the solution https://itnext.io/ingress-for-anthos-multi-cluster-ingress-and-global-service-load-balancing-c56c57b97e82

It is D. According to https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-ingress ... Multi Cluster Ingress's multi-cluster support satisfies many use cases including: Multi-regional, multi-cluster availability through health checking and traffic failover.

Anthos enables migration of legacy games [last business/tech requirement]. Since the question requires consideration of these requirements, this is the difference maker for option D.

For me is C. There is no necessity of Anthos or hybrid connectivity cluster. GKE and Global LB is enought

Needs ingress over multiple clusters which requires Multi Cluster Ingress or Antos for Ingress as it was previously known.

A is good to go. Anthos is an overkill here