Google Professional Cloud Network Engineer Question 441
Single answerGoogle Cloud PlatformYour organization has deployed a GKE cluster to host a web application. The application needs to expose its services to the internet using HTTP and HTTPS protocols. You want to ensure the scalability of the application while adhering to best practices for Google Cloud. Which configuration should you implement to set up an external load balancer for the GKE services?
- A
Use the GKE Gateway controller and configure a GatewayClass and Gateway resource.
- B
Manually create a Google Cloud HTTP(S) Load Balancer and attach it to the GKE cluster using a Backend Service.
- C
Use the GKE Ingress controller and define an Ingress resource in the Kubernetes cluster.
- D
Create a Network Endpoint Group (NEG) manually and attach it to a Google Cloud Load Balancer.
Show answer and explanation
Correct answer: C
Explanation
The GKE Ingress controller is the most appropriate solution for exposing GKE services to the internet using HTTP/HTTPS. It automates the integration with Google Cloud HTTP(S) Load Balancers and provides native Kubernetes management capabilities. While other options are technically possible, they are either less efficient or not recommended for most use cases. The Ingress controller simplifies configuration and ensures scalability and reliability for applications hosted on GKE.
- A. Incorrect.
The GKE Gateway controller is used for advanced Gateway API features but is currently not the most common method for exposing GKE services externally. It is still evolving compared to the GKE Ingress controller.
- B. Incorrect.
Manually creating a Google Cloud HTTP(S) Load Balancer and attaching it to a GKE cluster requires significant manual configuration and does not integrate seamlessly with Kubernetes. It is not the recommended approach.
- C. Correct.
The GKE Ingress controller is the recommended way to expose GKE services to the internet. Defining an Ingress resource allows Kubernetes-native management of HTTP/HTTPS traffic routing and integrates with Google Cloud HTTP(S) Load Balancers automatically.
- D. Incorrect.
Manually creating a Network Endpoint Group (NEG) and attaching it to a load balancer is a valid option but requires additional manual steps and is more error-prone compared to using the GKE Ingress controller.