Your team has created an application that is hosted on a Google Kubernetes Engine (GKE) cluster. You need to connect the application to a legacy REST service that is deployed in two GKE clusters in tw

Question

Options

• AUse Traffic Director with a sidecar proxy to connect the application to the service.
• BUse a proxyless Traffic Director configuration to connect the application to the service.
• CConfigure the legacy service's firewall to allow health checks originating from the proxy.
• DConfigure the legacy service's firewall to allow health checks originating from the application.
• EConfigure the legacy service's firewall to allow health checks originating from the Traffic Director

• A
  81% (25)
• B
  10% (3)
• D
  6% (2)
• E
  3% (1)

Explanation

Traffic Director with a sidecar proxy (Envoy) is the right solution for resilient cross-cluster, cross-region service mesh connectivity (Choice A). Traffic Director provides advanced load balancing, health checking, and traffic management across GKE clusters. Since sidecar proxies handle the actual traffic and health checks on behalf of the application, the legacy service's firewall must allow health check traffic originating from those proxies, not from the application pods directly (Choice C). Choice B (proxyless Traffic Director) does not use a sidecar, making health checks on a separate port more complex. Choice D is incorrect because with a sidecar proxy, health checks come from the proxy, not the application. Choice E is incorrect because Traffic Director is a control plane and does not send health checks itself.

No community discussion yet for this question.