Google Professional Cloud Network Engineer Question 442
Select 2Google Cloud PlatformYou are deploying a GKE cluster to host a web application that requires external HTTP(S) traffic from users worldwide. To ensure optimal performance and scalability, you want to configure a load balancer. Which of the following steps are necessary to correctly set up HTTP(S) Load Balancing using the GKE Ingress controller?
- A
Create a Kubernetes Ingress resource that references the necessary Services.
- B
Ensure that the Kubernetes Services referenced by the Ingress are of type NodePort.
- C
Configure a BackendConfig custom resource to enable advanced backend features such as session affinity or Cloud CDN.
- D
Manually create a Google Cloud HTTP(S) Load Balancer in the Cloud Console and link it to the GKE cluster.
- E
Verify that the GKE cluster has Cloud NAT enabled to allow backend instances to receive traffic from the external load balancer.
Show answer and explanation
Correct answers: A, C
Explanation
To set up HTTP(S) Load Balancing for a GKE cluster using the GKE Ingress controller, you must define a Kubernetes Ingress resource that specifies routing rules and references the necessary Services. Additionally, a BackendConfig custom resource can be used to enable advanced features like session affinity or Cloud CDN. The GKE Ingress controller automatically provisions and configures the external HTTP(S) Load Balancer, so manual creation of the load balancer or enabling Cloud NAT is not required. Services referenced by the Ingress should be of type ClusterIP to allow the Ingress controller to handle traffic routing properly.
- A. Correct.
Correct: To configure HTTP(S) Load Balancing, you must create a Kubernetes Ingress resource that specifies routing rules and references the relevant Services in the cluster.
- B. Incorrect.
Incorrect: Kubernetes Services referenced by the Ingress must be of type ClusterIP (default), as the GKE Ingress controller automatically handles the load balancer setup. NodePort is not required for Ingress.
- C. Correct.
Correct: A BackendConfig custom resource can be used to enable advanced load balancer features such as session affinity, Cloud CDN, or custom timeouts.
- D. Incorrect.
Incorrect: You do not manually create the HTTP(S) Load Balancer in the Cloud Console when using the GKE Ingress controller. The Ingress controller handles the creation and configuration of the load balancer automatically.
- E. Incorrect.
Incorrect: Cloud NAT is not required for this setup because the external HTTP(S) Load Balancer communicates with the GKE cluster using private IPs over the Google Cloud network.