Google Professional Cloud Network Engineer Question 443
Single answerGoogle Cloud PlatformYou are deploying a GKE-based application that requires external HTTPS access and must use a custom domain. The application is deployed across multiple regions, and you need to ensure low latency for users globally. Additionally, the backend pods are exposed using a Kubernetes Service of type ClusterIP. Which configuration should you use to meet these requirements?
- A
Use a GKE Gateway controller with a MultiCluster Service (MCS) and configure an HTTP(S) Load Balancer with a custom domain.
- B
Use the GKE Ingress controller with a Network Endpoint Group (NEG) and configure an HTTP(S) Load Balancer with a custom domain.
- C
Use the GKE Gateway controller with a Kubernetes Service of type
LoadBalancerand configure a global external HTTP(S) Load Balancer. - D
Use the GKE Ingress controller with a Kubernetes Service of type
NodePortand configure a regional external HTTP(S) Load Balancer.
Show answer and explanation
Correct answer: B
Explanation
The correct configuration for this scenario involves using the GKE Ingress controller with a Network Endpoint Group (NEG) to expose the backend ClusterIP service to an external HTTP(S) Load Balancer. The NEG allows the Load Balancer to route traffic directly to the pods, ensuring efficient traffic management. The HTTP(S) Load Balancer provides global distribution and custom domain support, making it suitable for the application's requirements.
- A. Incorrect.
This option is incorrect because while the GKE Gateway controller supports advanced traffic management, it does not automatically integrate with MultiCluster Services (MCS) in this scenario. MCS is also not required for this use case as the HTTP(S) Load Balancer can handle global traffic.
- B. Correct.
This option is correct because the GKE Ingress controller supports configuration with a NEG, which is required to expose the
ClusterIPservice to the HTTP(S) Load Balancer. Additionally, the HTTP(S) Load Balancer can handle global traffic distribution and custom domain configurations. - C. Incorrect.
This option is incorrect because the Kubernetes Service of type
LoadBalanceris not needed here. The NEG is required to expose theClusterIPservice for the HTTP(S) Load Balancer, and the GKE Gateway controller is less commonly used for this scenario. - D. Incorrect.
This option is incorrect because a Kubernetes Service of type
NodePortis not ideal for global traffic distribution. Additionally, a regional HTTP(S) Load Balancer does not meet the requirement for low-latency global access.