GCP Associate Cloud Engineer Practice Question 83: GKE Loadbalancer Service External
Google Cloud Associate Cloud Engineer · Test 9 · question 3 of 10
A team has a Deployment running in a GKE Standard cluster and needs to expose it to clients on the public internet with a stable external IP address, using only Kubernetes-native configuration and no extra Ingress controller setup. What is the simplest way to achieve this?
Show answer and explanation
Answer:
A Service of type LoadBalancer provisions a Google Cloud external Network Load Balancer with a stable public IP and forwards traffic to the Service's backing pods, which is exactly what a Kubernetes-native external exposure with minimal setup looks like.
Option B is wrong because a ClusterIP Service is only reachable from inside the cluster's virtual network; it has no external IP. Option C exposes a port on every node's IP, but those node IPs are not stable public endpoints and clients would have to know internal node addresses, which is fragile and not internet-facing by default. Option D bypasses the Service abstraction entirely, ties pods to specific node ports, and creates scheduling and security problems; it is not how external access is normally granted.
Reference: Service