How should you structure your source control repositories for both Infrastructure as Code (IaC) and application code when designing a system with three environments (development, QA, production), each deployed via Terraform with a GKE cluster, using Anthos Config Management for templated infrastructure-level resources, and adopting GitOps for all users (infrastructure operators and application owners)?

Exam-Like

• Cloud Infrastructure (Terraform) repository is shared: different directories are different environments • GKE Infrastructure (Anthos Config Management Kustomize manifests) repository is shared: different overlay directories are different environments • Application (app source code) repositories are separated: different branches are different features

77.8%

• Cloud Infrastructure (Terraform) repository is shared: different directories are different environments • GKE Infrastructure (Anthos Config Management Kustomize manifests) repositories are separated: different branches are different environments • Application (app source code) repositories are separated: different branches are different features

11.1%

• Cloud Infrastructure (Terraform) repository is shared: different branches are different environments • GKE Infrastructure (Anthos Config Management Kustomize manifests) repository is shared: different overlay directories are different environments • Application (app source code) repository is shared: different directories are different features

0.0%

• Cloud Infrastructure (Terraform) repositories are separated: different branches are different environments • GKE Infrastructure (Anthos Config Management Kustomize manifests) repositories are separated: different overlay directories are different environments • Application (app source code) repositories are separated: different branches are different

11.1%

Google Professional Cloud DevOps Engineer

Get started today

Comments