Google Professional Cloud Network Engineer Question 391
Single answerGoogle Cloud PlatformA company wants to deploy a global web application using Google Cloud. They need to ensure that their backend services can dynamically scale based on traffic demand and that the application is highly available. The application is deployed on Google Kubernetes Engine (GKE), and the company wants to use the best approach to configure their backend services. What is the recommended configuration in this scenario?
- A
Use a global Network Endpoint Group (NEG) with the GKE pods as endpoints.
- B
Use a zonal Network Endpoint Group (NEG) with Compute Engine instances as endpoints.
- C
Deploy an unmanaged instance group as the backend for the application.
- D
Use a zonal Network Endpoint Group (NEG) with the GKE pods as endpoints.
Show answer and explanation
Correct answer: D
Explanation
In Google Cloud, when configuring backend services for a GKE-based application, it is recommended to use zonal Network Endpoint Groups (NEGs) with the GKE pods as endpoints. Zonal NEGs allow you to directly link the backend service to the pods in a specific zone, ensuring dynamic scaling based on traffic demand and maintaining high availability. Global NEGs are not suitable for GKE pods as they are zonal resources.
- A. Incorrect.
Global NEGs are not supported for GKE pods because GKE pods are zonal resources. Instead, zonal NEGs should be used.
- B. Incorrect.
Using a zonal NEG with Compute Engine instances is not the best approach for a GKE-based application as the pods are not hosted on Compute Engine instances directly.
- C. Incorrect.
Unmanaged instance groups are not dynamically scalable and are not the best choice for a GKE-based application.
- D. Correct.
Zonal NEGs are the correct approach for GKE pods because they allow the pods to act as endpoints in a specific zone, supporting dynamic scalability and high availability.