Explanation:
The goal is to ensure consistency across development, staging, and production GKE environments by enforcing and installing network policies and a logging DaemonSet, with GitHub as the source of truth. Google-recommended practices emphasize GitOps for configuration management, which involves syncing configurations directly from Git to clusters to maintain desired state and automatically correct drift.
Option C is the best choice because Config Sync provides end-to-end GitOps for syncing and enforcing the desired state from GitHub, ensuring consistency without manual intervention. Cloud Build can be used for CI tasks like rendering, but Config Sync handles the core syncing functionality.
Ultimate access to all questions.
No comments yet.
Your team manages three Google Kubernetes Engine (GKE) environments: development, staging, and production, with GitHub repositories as the source of truth. To maintain consistency across these environments, you need to enforce network policies and deploy a logging DaemonSet on all GKE clusters following Google-recommended practices. What is the recommended approach?
A
Use Google Cloud Deploy to deploy the network policies and the DaemonSet. Use Cloud Monitoring to trigger an alert if the network policies and DaemonSet drift from your source in the repository.
B
Use Google Cloud Deploy to deploy the DaemonSet and use Policy Controller to configure the network policies. Use Cloud Monitoring to detect drifts from the source in the repository and Cloud Functions to correct the drifts.
C
Use Cloud Build to render and deploy the network policies and the DaemonSet. Set up Config Sync to sync the configurations for the three environments.
D
Use Cloud Build to render and deploy the network policies and the DaemonSet. Set up a Policy Controller to enforce the configurations for the three environments.