Answer-first summary for fast verification
Answer: Configure Anthos Config Management with the GitHub repository. When there is a change in the repository, use Anthos Config Management to apply the change.
To enforce constraint templates across GKE clusters with policy parameters stored in a GitHub repository and automatically applied upon changes, the most effective solution is to use Anthos Config Management. Anthos Config Management is designed for this exact purpose, enabling policy and configuration management across multiple clusters. It synchronizes configurations from a Git repository to your clusters, ensuring that the desired state is maintained. Option C correctly describes this approach. Option A involves an unnecessary roundtrip through Cloud Build and the gcloud CLI, which is less efficient for this specific need. Option B incorrectly suggests using Anthos Service Mesh, which is unrelated to policy enforcement. Option D mentions Config Connector, which is used for managing Google Cloud resources through Kubernetes, not for enforcing policies across clusters.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
To enforce constraint templates with policy parameters across your Google Kubernetes Engine (GKE) clusters, including restrictions on the Kubernetes API, while storing these parameters in a GitHub repository and ensuring automatic application upon changes, what steps should you take?
A
Set up a GitHub action to trigger Cloud Build when there is a parameter change. In Cloud Build, run a gcloud CLI command to apply the change.
B
When there is a change in GitHub. use a web hook to send a request to Anthos Service Mesh, and apply the change.
C
Configure Anthos Config Management with the GitHub repository. When there is a change in the repository, use Anthos Config Management to apply the change.
D
Configure Config Connector with the GitHub repository. When there is a change in the repository, use Config Connector to apply the change.