QuestionQ335

Integrating applications with Google Cloud services

Your team has developed an application hosted on a Google Kubemetes Engine (GKE) cluster. You need to connect the application to a legacy REST service deployed across two GKE clusters in two separate regions. You want the connection to the legacy service to be resilient and to require the fewest steps. You also need to run probe-based health checks for the legacy service on a separate port. How should you configure the connection?

Choose two
  • A Use Traffic Director with a sidecar proxy to connect the application to the service.
  • B Set up a proxyless Traffic Director configuration for the application.
  • C Configure the legacy service's firewall to allow health checks originating from the sidecar proxy.
  • D Configure the legacy service's firewall to allow health checks originating from the application.
  • E Configure the legacy service's firewall to allow health checks originating from the Traffic Director control plane.
Explanation

Traffic Director with an Envoy sidecar proxy supports HTTP/REST traffic and can route to healthy endpoints across regions for resilient failover. Proxyless Traffic Director is for xDS-enabled gRPC applications, not a general REST-client configuration. Traffic Director backend health checks use Google Cloud health-check probers and support an explicitly configured health-check port, so the legacy service must allow those control-plane-managed probes through its firewall.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!