Exam Professional Cloud DevOps Engineer topic 1 question 151 discussion

B. So they can only create with pipeline.

Config Connector allows you to manage Google Cloud resources through Kubernetes-style declarative configuration. By installing and configuring Config Connector in GKE, you can define and manage cloud resources using Kubernetes manifests, ensuring that infrastructure configurations are reconciled periodically to avoid configuration drift

Option A is the recommended approach for managing infrastructure as code and avoiding configuration drift in a Google Kubernetes Engine (GKE) environment while following Google-recommended practices. Config Connector is a Kubernetes extension that allows you to manage Google Cloud resources as Kubernetes objects. By installing and configuring Config Connector in GKE, you can declare your cloud resources as Kubernetes CustomResourceDefinitions (CRDs) and have them managed by Kubernetes controllers. This ensures that the desired state of your infrastructure is continuously reconciled with the actual state, helping to prevent configuration drift. Config Connector aligns with the GitOps methodology, providing a declarative way to manage cloud resources and maintain consistency in your environment.

Config Connector's controllers eventually reconcile your environment with your desired state. https://cloud.google.com/config-connector/docs/overview

Why not A? https://cloud.google.com/blog/products/containers-kubernetes/anthos-config-management-config-controller-available-on-gke Config controller leverages config connector, config controller includes config-synct/gcp-cloud-resource-creation/policy-sync, it 'gitops', 'reconcile', 'taking-care-of-gcp-cloud-resource'

I also vote for B

I think the answer B is correct.