Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Google Cloud Certified Professional Cloud Developer · Google Cloud
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The correct answer is A. Configure a GKE Ingress resource. Here's why: Ingress for External Load Balancing: Ingress is the Kubernetes resource specifically designed for managing external HTTP(S) traffic to services within your cluster. When you create an Ingress resource, GKE automatically provisions and configures a Cloud Load Balancing HTTP(S) load balancer to route traffic to your application.
Let's break down why the other options are incorrect: B. Configure a GKE Service resource: Services in Kubernetes are used to expose applications within the cluster. While you can create a Service of type LoadBalancer , this will create an internal load balancer within the cluster, not an external one. C. Configure a GKE Ingress resource with type: LoadBalancer: Ingress resources don't have a type field. The LoadBalancer type is used for Services, not Ingress. D. Configure a GKE Service resource with type: LoadBalancer: This would create an internal load balancer within the cluster, not an external one.
A. Configure a GKE Ingress resource. This option correctly configures the Ingress resource which is designed to expose HTTP and HTTPS routes from outside the cluster to services within the cluster. B. Configure a GKE Service resource. This option only exposes the application internally within the cluster unless the service type is specified as LoadBalancer. C. Configure a GKE Ingress resource with type: LoadBalancer. This option is incorrect because Ingress resources do not have a type: LoadBalancer property. The Ingress resource itself manages the creation of a load balancer. D. Configure a GKE Service resource with type: LoadBalancer. This option creates a TCP/UDP load balancer, not an HTTP(S) load balancer, which does not meet the requirements for an HTTP(S) load balancer.