Google Professional Cloud Network Engineer Question 394
Single answerGoogle Cloud PlatformYou are designing a load-balanced application on Google Cloud that serves both HTTP and HTTPS traffic. The application needs to route traffic to backend instances based on their proximity to users. Furthermore, the backend instances are deployed on Compute Engine VMs and a Kubernetes cluster in the same region. Which configuration should you use to set up the backend services?
- A
Use a global external HTTP(S) load balancer with zonal network endpoint groups (NEGs) for both the Compute Engine VMs and Kubernetes pods.
- B
Use a regional external HTTP(S) load balancer with instance groups for the Compute Engine VMs and a Kubernetes Service for the Kubernetes pods.
- C
Use a global external HTTP(S) load balancer with regional network endpoint groups (NEGs) for the Compute Engine VMs and zonal network endpoint groups (NEGs) for the Kubernetes pods.
- D
Use a regional internal HTTP(S) load balancer with zonal network endpoint groups (NEGs) for both the Compute Engine VMs and Kubernetes pods.
Show answer and explanation
Correct answer: A
Explanation
To serve HTTP and HTTPS traffic with proximity-based routing across both Compute Engine VMs and Kubernetes pods, you should use a global external HTTP(S) load balancer. Zonal NEGs are ideal for referencing specific endpoints, such as VM instances and Kubernetes pods, enabling precise traffic routing to the closest available backend resources.
- A. Correct.
Correct. A global external HTTP(S) load balancer combined with zonal network endpoint groups (NEGs) is the right configuration. Zonal NEGs allow you to reference Compute Engine VMs and Kubernetes pods individually, providing precise traffic routing and proximity-based load balancing.
- B. Incorrect.
Incorrect. Regional external HTTP(S) load balancers are not designed for global traffic. Additionally, using a Kubernetes Service instead of NEGs does not provide sufficient granularity for proximity-based routing.
- C. Incorrect.
Incorrect. Regional NEGs are not suitable for Compute Engine VMs in this scenario, as zonal NEGs provide better granularity. Mixing regional and zonal NEGs is also not recommended for this use case.
- D. Incorrect.
Incorrect. Regional internal HTTP(S) load balancers are used for internal traffic, not for serving external HTTP and HTTPS traffic. This does not meet the requirements of the scenario.