An enterprise runs microservice workloads across Google Kubernetes Engine (GKE) on Google Cloud, on-premises VMware environments, and AWS. The organization requires a centralized management strategy to achieve the following goals: Group and administer distributed clusters across environments as a single logical unit. Automatically synchronize declarative configurations and enforce compliance policies across all clusters from a centralized Git repository. Implement zero-trust security with mutual TLS (mTLS) encryption and gain deep observability into cross-cluster service communications. Which combination of GKE Enterprise capabilities should the cloud architect recommend?

Group the clusters into a GKE fleet, use Config Sync and Policy Controller for configuration and compliance, and deploy Cloud Service Mesh for mTLS and telemetry.: ### What the GKE Enterprise Solution Is **GKE Enterprise** (formerly Anthos) provides an integrated hybrid and multicloud application platform. It enables organizations to run, manage, and secure Kubernetes workloads across Google Cloud, on-premises data centers, and third-party clouds such as AWS and Azure through a unified control plane. ### How It Meets the Requirements - **Unified Cluster Administration**: **GKE Fleets** logically group heterogeneous Kubernetes clusters across Google Cloud, AWS, and on-premises into a unified management plane, allowing administrators to apply configurations and policies holistically. - **Declarative Configuration and Compliance**: **Config Sync** acts as a managed GitOps engine to automatically deploy and reconcile Kubernetes configurations from a central Git source of truth. **Policy Controller** enforces programmable security constraints and compliance rules across all registered fleet clusters. - **Zero-Trust Security and Observability**: **Cloud Service Mesh** establishes service-to-service mutual TLS (**mTLS**) authentication and encryption in transit across hybrid environments without requiring application code changes, while capturing rich telemetry, service graphs, and metrics in **Google Cloud Observability**. ### Key Advantages and Capabilities - **Fleet-Wide Normalization**: Leverages the concept of sameness across namespaces, identity, and services across all cloud and on-premises clusters. - **GitOps-Driven Automation**: Continuously reconciles cluster state against declarative configurations to prevent configuration drift. - **Fine-Grained Traffic Control**: Manages Layer 7 routing, canary releases, circuit breakers, and fault injection across distributed clusters. - **Comprehensive Telemetry**: Automatically collects metrics, logs, and distributed traces powered by **Cloud Monitoring**, **Cloud Logging**, and **Cloud Trace**. ### Why This Is Optimal This architecture utilizes native GKE Enterprise features specifically built for hybrid and multicloud governance. It avoids custom operational tooling and delivers unified multi-cluster policy enforcement, declarative synchronization, and cross-cluster service mesh security.

StudyCerts

Gke Enterprise Fleet Management Service Mesh 2 | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Gke Enterprise Fleet Management Service Mesh 2

Section: Integration with on-premises/multicloud environments

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 runs microservice workloads across Google Kubernetes Engine (GKE) on Google Cloud, on-premises VMware environments, and AWS. The organization requires a centralized management strategy to achieve the following goals:

Group and administer distributed clusters across environments as a single logical unit.
Automatically synchronize declarative configurations and enforce compliance policies across all clusters from a centralized Git repository.
Implement zero-trust security with mutual TLS (mTLS) encryption and gain deep observability into cross-cluster service communications.

Which combination of GKE Enterprise capabilities should the cloud architect recommend?

Migrate all workloads to Google Cloud VMware Engine, manage cluster manifests using Config Connector, enforce security with Container-Optimized OS, and expose internal services via the Connect gateway with HTTP load balancing.

Deploy Knative serving across all external virtual machines, establish Cloud Interconnect for configuration syncing, use Binary Authorization to enforce runtime policies, and collect telemetry using Container Threat Detection.

Group the clusters into a GKE fleet, use Config Sync and Policy Controller for configuration and compliance, and deploy Cloud Service Mesh for mTLS and telemetry.

Connect all clusters using VPC Network Peering, configure Deployment Manager for cluster synchronization, apply IAM custom roles for policy governance, and implement Cloud NAT for mTLS communications.

Professional Cloud Architect

Gke Enterprise Fleet Management Service Mesh 2

Related questions