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

Question

Options

• AUse Traffic Director with a sidecar proxy to connect the application to the service.
• BSet up a proxyless Traffic Director configuration for the application.
• CConfigure the legacy service's firewall to allow health checks originating from the sidecar 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
  63% (30)
• B
  6% (3)
• D
  8% (4)
• E
  23% (11)

Explanation

Traffic Director with a sidecar proxy (Envoy) is GCP's managed service mesh control plane. It provides cross-cluster, cross-region load balancing and resilience features (retries, circuit breaking, failover) out of the box, satisfying the resiliency requirement with minimal configuration steps. The sidecar proxy is what actually performs health checks, so the legacy service's firewall must allow health check traffic originating from the sidecar proxy (C). Option B (proxyless Traffic Director) does not support HTTP/REST services well and cannot perform sidecar-based probe health checks on a separate port. Option D is incorrect because health checks flow from the sidecar, not the application pod directly. Option E is incorrect because Traffic Director's control plane does not generate health check traffic itself - the data-plane sidecar does.

No community discussion yet for this question.