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.
Your enterprise manages multiple Google Kubernetes Engine (GKE) clusters grouped into staging and production fleets. Your platform engineering team needs to implement a fleet-wide GitOps architecture using Config Sync and Policy Controller that satisfies the following requirements:
Which configuration architecture should you implement?
This design bundles application source code and configuration in a single monorepo, manages all namespace and platform configs via root-level RootSync objects, and applies the client.lifecycle.config.k8s.io/mutation: ignore annotation to Policy Controller constraints.
RootSync fails to delegate ownership safely; it requires granting developers broad access or bottlenecks all changes through the platform team.mutation: ignore instructs Config Sync to ignore drift on Policy Controller constraints, allowing unauthorized local mutations and defeating declarative compliance enforcement.RepoSync prevents granular tenant isolation.mutation: ignore undermines Policy Controller governance and drift remediation.A single developer team required a rapid proof-of-concept where security policies were advisory and application code changes directly determined cluster deployments without separation of duties.
This model relies on the legacy hierarchical repository format with reserved directories (cluster/, namespaces/, system/), maintains environment differences via long-lived Git branches, and relies on Node-level Compute Engine default service accounts (gcenode) for authentication.
RepoSync objects (which require unstructured format) and complicating configuration sharing across teams.gcenode): This authentication method requires disabling Workload Identity Federation for GKE, violating least-privilege security principles and the requirement to eliminate static node-wide credential sharing.RepoSync objects.gcenode grants broad node-level permissions rather than granular per-reconciler identity.You were maintaining a legacy single-repo deployment requiring abstract namespace inheritance without delegated namespace administration or Workload Identity Federation.
This architecture uses Config Sync with a multi-repository model that separates root platform configurations from delegated namespace configurations, managed through declarative Kubernetes Custom Resources (RootSync and RepoSync) across GKE Enterprise fleets.
RootSync managed by the platform team deploys cluster-wide RBAC and declarative Policy Controller constraints across all fleet clusters.RepoSync objects instantiate dedicated namespace reconcilers with limited permissions (RoleBinding scoped to the target namespace), allowing app teams to deploy resources without granting cluster-admin access.This approach aligns with Google Cloud recommended enterprise patterns by combining the delegated authority of multi-repo Config Sync, the declarative enforcement of Policy Controller, and IAM-based Workload Identity Federation.
This approach uses Kubernetes Job manifests synchronized via RootSync to run imperative scripts, relies on ClusterSelectors and DRY (Don't Repeat Yourself) parameter substitutions in a shared monorepo, and uses static Kubernetes Secrets containing personal access tokens for authentication.
Job objects have immutable fields and reconcile upon starting rather than completion. Config Sync continuously attempts to recreate deleted or TTL-expired Jobs, causing reconciliation failures and drift loops.ClusterSelectors and complex DRY transformations makes it difficult to ascertain the final rendered state of individual clusters across staging and production fleets.Your deployment relied entirely on transient one-off tasks managed outside of declarative reconcilers and lacked access to Google Cloud IAM integration.
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