Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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?
This option attempts to configure cross-cluster communication by manually authoring a ServiceImport custom resource inside Cluster A that statically references node IP addresses from Cluster B, while continuing to query the local .svc.cluster.local DNS domain.
.svc.cluster.local DNS zone is cluster-scoped and cannot resolve endpoints spanning multiple clusters; multi-cluster discovery requires the .svc.clusterset.local domain..svc.cluster.local namespace is reserved strictly for single-cluster service discovery.You were using legacy NodePort routing with manual DNS overrides or static external endpoints rather than GKE Fleet Multi-cluster Services.
Attempting to manually write to controller-managed CRDs like ServiceImport leads to reconciliation conflicts, as the MCS controller will overwrite or reject manual modifications.
Multi-cluster Ingress (MCI) is a Google Cloud fleet feature designed for North-South ingress traffic management. It provisions a Global External Application Load Balancer or Internal Application Load Balancer at the edge of the network to direct incoming client traffic to backend clusters.
..svc.clusterset.local DNS service discovery for inter-pod calls.MultiClusterIngress and MultiClusterService resources to program Google Cloud load balancer forwarding rules and URL maps.ClusterIP services are strictly local to a single cluster and cannot be directly targeted across clusters by external load balancers without multi-cluster abstractions.The requirement were to expose the payment service to external public Internet clients or external corporate networks requiring global edge termination and DDoS mitigation.
While Multi-cluster Ingress and Multi-cluster Services are complementary fleet features, MCS is specifically optimized for private East-West pod-to-pod networking, whereas MCI is intended for North-South ingress.
This option suggests exporting the service from only one cluster and creating custom Cloud DNS forwarding zones or conditional forwarding rules to rewrite local .svc.cluster.local DNS lookups to point directly to remote cluster resources.
svc.clusterset.local; manually configuring rewrite rules for .svc.cluster.local disrupts standard intra-cluster Kubernetes DNS resolution.clusterset.local based on exported services..cluster.local zones causes collisions with local cluster-scoped services.You were integrating non-Kubernetes legacy virtual machines via custom Cloud DNS private forwarding rather than using GKE Fleet features.
To ensure consistent endpoint aggregation across clusters, ServiceExport resources must be applied in every cluster hosting backends for that specific service.
Multi-cluster Services (MCS) for Google Kubernetes Engine (GKE) extends the reach of Kubernetes Service discovery and invocation across multiple GKE clusters within an enterprise fleet. By leveraging the open-source Kubernetes MCS API standard (net.gke.io/v1), workloads across participating fleet clusters can discover and communicate with services running in other clusters without requiring public exposure or complex custom network routing.
..svc.clusterset.local.clusterset.local).Deploying identical services in both clusters and creating a ServiceExport in each is Google's recommended architecture for cross-cluster East-West high availability. It abstracts infrastructure boundaries and provides built-in endpoint health tracking and traffic failover across GKE fleets.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated