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 organization is establishing a centralized GitOps workflow across staging and production environments to enforce policy-as-code and automatically detect and reconcile configuration drift for Google Cloud and Kubernetes resources using Google Cloud Config Sync.
The team has established the following technical requirements:
namespaces/ or cluster/)./deployments/prod directory on the main branch.Which configuration should you implement to establish this automated drift reconciliation pipeline?
A RepoSync resource is designed for namespace-level synchronization in Config Sync, allowing individual application teams to manage resources strictly within their delegated namespaces. The gatekeeper-system namespace is dedicated to OPA Gatekeeper and Policy Controller components, not root GitOps synchronization.
RepoSync cannot manage cluster-wide configurations or create resources outside its designated target namespace, failing the requirement to manage both cluster-scoped and namespace-scoped infrastructure.spec.sourceFormat to hierarchy mandates a strict, predefined directory layout (such as cluster/ and namespaces/), directly violating the requirement for flexible folder organization.config-management-system, not gatekeeper-system.The requirement called for delegating self-service policy management to a tenant team strictly restricted to their own isolated namespace using standard hierarchical layouts.
This option attempts to create a RootSync resource inside the standard Kubernetes default namespace while configuring the synchronizer with hierarchical formatting.
config-management-system namespace for RootSync custom resources. Deploying RootSync in default causes the Config Sync operator to ignore the object completely, resulting in no synchronization or drift detection.spec.sourceFormat: hierarchy forces the sync engine to parse the repository according to strict structural rules (namespaces/, clusterregistry/, cluster/), which breaks when teams organize YAML files freely.HEAD is the default revision fallback, best practices for multi-environment promotion (e.g., staging vs. production) require pinning specific branch references like main or environment tags.config-management-system are unmanaged by the Config Sync root reconciler.The cluster utilized legacy Anthos Config Management hierarchical repos and allowed global objects in unmanaged namespaces, which is not supported in modern Config Sync architectures.
The ConfigManagement custom resource in kube-system represents the legacy v1 configuration mechanism for Anthos Config Management before the introduction of multidimensional RootSync and RepoSync APIs.
configsync.gke.io/v1beta1 API (RootSync/RepoSync) located in config-management-system rather than monolithic ConfigManagement objects in kube-system.ConfigManagement operator does not provide multi-source syncing capabilities or modern unstructured repository controls per environment directory as cleanly as RootSync.config-management-system.You were maintaining an obsolete legacy ACM installation (version 1.6 or earlier) where the operator was managed via a single cluster-wide custom resource.
A RootSync object is a Kubernetes custom resource defined by Config Sync (configsync.gke.io/v1beta1) residing in the config-management-system namespace. It configures the root synchronizer agent responsible for pulling configurations from an authoritative version control repository (such as Git or OCI registries) and continuously reconciling cluster state against the declared manifests.
RootSync operates with root-level privileges to manage both cluster-scoped resources (e.g., ClusterRoles, CRDs, Google Cloud resources via Config Connector) and namespace-scoped resources across the cluster.spec.sourceFormat: unstructured enables the unstructured repository format. Unlike the legacy hierarchical format, unstructured repositories do not enforce rigid top-level folder conventions like namespaces/, cluster/, or system/, allowing teams to organize manifests by application, environment, or microservice.spec.git.dir to /deployments/prod and spec.git.revision to main explicitly instructs Config Sync to sync the specific environment configurations from the designated Git branch.Using a native RootSync resource configured with unstructured formatting is the Google-recommended pattern for scalable GitOps architectures. It provides root-level control while avoiding the architectural limitations of strict hierarchical directory trees.
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