Gke Fleet Registration Workload Identity Federation

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 operates multiple Google Kubernetes Engine (GKE) clusters across separate Google Cloud projects for production and staging environments. A DevOps engineer is tasked with registering these heterogeneous clusters into a centralized fleet host project to establish unified Fleet Workload Identity for seamless, cross-cluster credential exchange and service authentication.

Which configuration requirement and architectural constraint must the engineer apply when implementing this fleet architecture?

Register the clusters using lightweight memberships across projects to minimize resource overhead, and manually configure custom Workload Identity pools in each spoke project.

Register the clusters in their local spoke projects first, and dynamically unregister and re-register them to the central fleet host project during runtime to migrate their identity pools seamlessly.

Register the clusters to the central fleet host project with standard full memberships, ensuring lightweight memberships are avoided because they disable Fleet Workload Identity Federation.

Attach the heterogeneous clusters to the central fleet using Workforce Identity Federation mapped to individual team scopes to issue cross-cluster service account tokens.

Professional Cloud DevOps Engineer

Gke Fleet Registration Workload Identity Federation

Related questions