Google Cloud Professional Cloud Architect · Free practice question 1 of 12
Config Sync GitOps across a cluster fleet
Thornbury Retail operates 25 GKE clusters across four regions. Platform engineers want namespaces, RBAC bindings and network policies to be identical on every cluster, defined in a Git repository, and automatically corrected if someone changes them by hand. What should the architect recommend?
- A.Manifests stored in a Cloud Storage bucket that each team copies from
- B.A nightly script that applies the manifests to each cluster with kubectl and emails a report of any failures
- C.Config Sync, syncing configuration from the Git repository to every fleet cluster
- D.A written checklist of required settings for each cluster owner
Show answer and explanation
Correct answer: C. Config Sync, syncing configuration from the Git repository to every fleet cluster
Why: Config Sync continuously reconciles clusters against a Git source of truth, applying changes everywhere and reverting manual drift. A nightly kubectl script leaves drift in place for up to a day and needs maintenance. Shared buckets and checklists depend on people applying them consistently.
More free Google Cloud Professional Cloud Architect questions
- Chirp speech model for call transcription
- AlloyDB read pools for read scaling
- VM Manager OS patch management
- BigQuery long-term storage pricing
- Feature Store against training-serving skew
- Autoclass for unpredictable object access
- Workflows orchestrating serverless steps
- Managed Service for Apache Airflow for complex DAGs
- Cloud DNS failover routing policy
- Datastream change data capture into BigQuery
- Cloud Asset Inventory IAM policy analysis