Gke Fleet Multi Cluster Services Serviceexport Configuration

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise organization runs microservices across two VPC-native Google Kubernetes Engine (GKE) clusters registered to the same fleet host project within a Shared VPC. A frontend workload running in Cluster A must reliably discover and invoke a backend payment service deployed redundantly in both Cluster A and Cluster B, with automatic traffic distribution and cross-cluster failover.

Which configuration should you implement using Multi-cluster Services (MCS) to meet these requirements?

Create a MultiClusterIngress resource in Cluster A that routes traffic directly to Cluster B using standard Kubernetes ClusterIP Services, and direct the frontend to query external Global HTTP(S) Load Balancer IP addresses.

Deploy the payment service in Cluster B only, manually define a ServiceImport resource in Cluster A pointing to the Cluster B node IPs, and configure the frontend to resolve backend targets using the .svc.cluster.local domain.

Deploy the payment service with identical names and namespaces in both clusters, apply a ServiceExport object matching that name and namespace in each cluster, and configure the frontend to target the service at ..svc.clusterset.local.

Export the payment service from Cluster A using a ServiceExport resource, and configure an external Cloud DNS forwarding zone to rewrite internal .svc.cluster.local requests to the private IP of Cluster B.

Professional Cloud DevOps Engineer

Gke Fleet Multi Cluster Services Serviceexport Configuration

Related questions