PROFESSIONAL-CLOUD-DEVELOPER · Question #18
Your application is deployed in a Google Kubernetes Engine (GKE) cluster. You want to expose this application publicly behind a Cloud Load Balancing HTTP(S) load balancer. What should you do?
The correct answer is A. Configure a GKE Ingress resource.. A GKE Ingress resource directly provisions and manages a Google Cloud HTTP(S) Load Balancer (Layer 7), which is exactly what the question requires. Ingress handles URL-based routing, SSL termination, and integrates with Cloud Armor and IAP. A GKE Service with type: LoadBalancer (
Question
Your application is deployed in a Google Kubernetes Engine (GKE) cluster. You want to expose this application publicly behind a Cloud Load Balancing HTTP(S) load balancer. What should you do?
Options
- AConfigure a GKE Ingress resource.
- BConfigure a GKE Service resource.
- CConfigure a GKE Ingress resource with type: LoadBalancer.
- DConfigure a GKE Service resource with type: LoadBalancer.
How the community answered
(25 responses)- A80% (20)
- B12% (3)
- C4% (1)
- D4% (1)
Explanation
A GKE Ingress resource directly provisions and manages a Google Cloud HTTP(S) Load Balancer (Layer 7), which is exactly what the question requires. Ingress handles URL-based routing, SSL termination, and integrates with Cloud Armor and IAP. A GKE Service with type: LoadBalancer (option D) provisions a Network Load Balancer (Layer 4 TCP/UDP), not an HTTP(S) load balancer. A plain Service (option B) with no type only creates a ClusterIP or NodePort, not a public LB. Option C is incorrect syntax - Ingress resources do not use a type: LoadBalancer field; that field belongs to Services.
Topics
Community Discussion
No community discussion yet for this question.