Your team has created an application that is hosted on a GKE cluster. You need to connect the application to a REST service that is deployed in two GKE clusters in two different regions. How should yo

Question

Options

• AUse Cloud Service Mesh with sidecar proxies to connect the application to the REST service.
• BUse Cloud Service Mesh with proxyless gRPC to connect the application to the REST service.
• CConfigure the REST service's firewall to allow health checks originating from the GKE service's IP
• DConfigure the REST service's firewall to allow health checks originating from the GKE control
• EConfigure the REST service's firewall to allow health checks originating from the GKE check

• A
  74% (32)
• B
  16% (7)
• C
  2% (1)
• D
  7% (3)

Explanation

Option A is correct because Cloud Service Mesh with sidecar proxies (Envoy) provides automatic service discovery, load balancing, traffic management, and health checking across multi-cluster GKE deployments - ideal for connecting a REST service across two regions. Option E is correct because Google Cloud's health checking systems originate from specific IP ranges (35.191.0.0/16 and 130.211.0.0/22), and the REST service's firewall must allow traffic from these ranges for health checks to succeed. Option B (proxyless gRPC) is designed for gRPC workloads, not REST. Option C (firewall rules from the GKE service's IP) is incorrect because health checks originate from Google's health check infrastructure, not from service IPs. Option D (from the GKE control plane) is similarly incorrect for health check source IPs.

No community discussion yet for this question.