PROFESSIONAL-CLOUD-DEVELOPER · Question #128
You manage an application that runs in a Compute Engine instance. You also have multiple backend services executing in stand-alone Docker containers running in Compute Engine instances. The Compute En
The correct answer is A. Traffic Director. Traffic Director is Google Cloud's fully managed service mesh traffic control plane that supports advanced traffic management capabilities including routing based on HTTP headers, URL paths, and other request attributes. It is designed for internal service-to-service communicatio
Question
You manage an application that runs in a Compute Engine instance. You also have multiple backend services executing in stand-alone Docker containers running in Compute Engine instances. The Compute Engine instances supporting the backend services are scaled by managed instance groups in multiple regions. You want your calling application to be loosely coupled. You need to be able to invoke distinct service implementations that are chosen based on the value of an HTTP header found in the request. Which Google Cloud feature should you use to invoke the backend services?
Options
- ATraffic Director
- BService Directory
- CAnthos Service Mesh
- DInternal HTTP(S) Load Balancing
How the community answered
(30 responses)- A77% (23)
- B10% (3)
- C3% (1)
- D10% (3)
Explanation
Traffic Director is Google Cloud's fully managed service mesh traffic control plane that supports advanced traffic management capabilities including routing based on HTTP headers, URL paths, and other request attributes. It is designed for internal service-to-service communication and integrates with Envoy proxies running alongside your services. This enables the header-based routing logic described without changes to the application code. Option B (Service Directory) is a managed registry for service endpoints, not a traffic routing solution. Option C (Anthos Service Mesh) provides similar capabilities but is a heavier platform requiring more infrastructure investment. Option D (Internal HTTP(S) Load Balancing) supports URL-map-based routing but does not natively support arbitrary HTTP header value-based routing to distinct backend implementations in the same flexible way Traffic Director does.
Topics
Community Discussion
No community discussion yet for this question.