Ans is D A: No, Doest make sense B: Who says that we are using a premium tier? C: This does not help with the network cost? D: Ok :) Costs associated with a load balancer are charged to the project containing the load balancer components. Because of these benefits, container-native load balancing is the recommended solution for load balancing through Ingress. When NEGs are used with GKE Ingress, the Ingress controller facilitates the creation of all aspects of the L7 load balancer. This includes creating the virtual IP address, forwarding rules, health checks, firewall rules, and more. https://cloud.google.com/architecture/best-practices-for-running-cost-effective-kubernetes-applications-on-gke

D 100%

Agree with D over B

I'll go with D. AS HTTP LB will help to reduce the costs. In question it is not mentioned that premium tier is used, so we can't assume that premium tier is used (eventhough it is default network tier) and go with B. So D is the correct answer.

Answer B

Answer B

I go for B, as "Premium" is the default tier. D could be nice, but totally relies on the architecture of the application. If the application needs to be global or re-route lots of requests, a LB makes no miracles.

D -configuring the load balancer as ingress

I am confused between B and D. Default network is Premium which is costly, so changing to Standard also make sense. D is also correct when you'll have multiple endpoints and Google also suggested to LB. But, I'll go with (B) as it'll reduce some cost.

To reduce network costs for the mobile phone game running on a Google Kubernetes Engine (GKE) cluster, the recommended approach is to use a Google Cloud HTTP Load Balancer as Ingress. This option is the best as it provides several advantages such as scalability, cost-effectiveness, and security.

Premium tier is the default, so... switching to Standard tier is the only answer here that directly refers to costs

A Google Cloud HTTP Load Balancer can help reduce network costs by efficiently routing traffic to the backend services running on the GKE cluster. By configuring the load balancer as ingress, it will receive all incoming traffic and then route it to the appropriate backend service. This eliminates the need for each service to have its own external IP address, which can be costly in terms of network usage. Option A, Configure the VPC as a Shared VPC Host project, is not relevant to reducing network costs for a mobile phone game running on a GKE cluster. Option B, Configure your network services on the Standard Tier, is also not relevant to reducing network costs. The Standard Tier is a premium network service that offers better performance but is more expensive than the other tiers. Option C, Configure your Kubernetes cluster as a Private Cluster, is not directly relevant to reducing network costs. A private cluster restricts access to the Kubernetes API server to a private IP address range, which can improve security but does not necessarily reduce network costs.

Ans is B - Stanard Tier

Option C would only be applicable if the Kubernetes cluster had not yet been created, and the private cluster feature was enabled at cluster creation time. Also the application is serving HTTP requests from users and it could be bad if stop it. The option D on the other hand, configuring a Google Cloud HTTP Load Balancer as Ingress, would not have a direct impact on reducing network costs. It would instead provide a more efficient way of managing and distributing incoming traffic to the Kubernetes cluster, which may indirectly help reduce costs, but not as much as the option C.

i think it is C. private cluster has no public IP addresses, internal IP addresses are no charged, external traffic via CND with a public IP addresses is no charged

D is the answer. https://cloud.google.com/architecture/best-practices-for-running-cost-effective-kubernetes-applications-on-gke#use_container-native_load_balancing_through_ingress Container-native load balancing lets load balancers target Kubernetes Pods directly and to evenly distribute traffic to Pods by using a data model called network endpoint groups (NEGs). This approach improves network performance, increases visibility, enables advanced load-balancing features, and enables the use of Traffic Director, Google Cloud's fully managed traffic control plane for service mesh. Because of these benefits, container-native load balancing is the recommended solution for load balancing through Ingress.

Cant be B Standard tier is regional and can't serve request from global users. k8s requires LBs to direct traffic, standard tier do not support that. correct me if i'm wrong but I would go with D