Google Professional Cloud Network Engineer Question 393
Single answerGoogle Cloud PlatformYou are setting up a backend service for an application deployed on Google Cloud. The application requires low-latency connectivity to instances located in a specific Google Cloud region. Additionally, you want to ensure the backend service can handle auto-scaling based on traffic demand. Which backend configuration should you use?
- A
Create a backend service with an unmanaged instance group to handle the traffic.
- B
Use a network endpoint group (NEG) to define the backend, ensuring connectivity to regional resources.
- C
Configure a global backend service with managed instance groups to distribute traffic across multiple regions.
- D
Set up a backend service with zonal unmanaged instance groups for better control over specific zones.
Show answer and explanation
Correct answer: B
Explanation
The correct answer is to use a network endpoint group (NEG) for the backend configuration. NEGs offer low-latency connectivity to regional resources, and they integrate seamlessly with load balancing features, which makes them ideal for auto-scaling based on traffic demand. The other options either do not meet the regional requirement or lack the scalability required for the scenario.
- A. Incorrect.
Unmanaged instance groups are not recommended for auto-scaling or integrating with backend services that require dynamic scaling. They are manually managed and do not offer the flexibility required for traffic demand scaling.
- B. Correct.
Network endpoint groups (NEGs) are ideal for connecting backend services to specific regional resources. They support load balancing and low-latency access to instances within a region, which aligns with the requirements specified.
- C. Incorrect.
Global backend services with managed instance groups are used for distributing traffic across multiple regions. However, the scenario specifically requires a regional solution, making this option unsuitable.
- D. Incorrect.
Zonal unmanaged instance groups provide fine-grained control within a specific zone but lack the flexibility and scalability needed for handling traffic demand dynamically. They are also not designed for regional resource connectivity.