Exam Professional Cloud DevOps Engineer topic 1 question 152 discussion

A. This follows best practices for structuring repositories in a GitOps workflow while maintaining clear separation between infrastructure and application code. - Cloud Infrastructure (Terraform) repository is shared with different directories for different environments. This ensures all infrastructure is managed from a single place while maintaining separation for different environments. - GKE Infrastructure (Anthos Config Management Kustomize manifests) repository is shared with different overlay directories for different environments. Kustomize overlays are the recommended way to manage configuration differences across environments. - Application repositories are separated, with different branches representing different features. This allows application teams to work independently while maintaining best practices for Git-based development.

Why? "Cloud Infrastructure (Terraform) repository is shared: different directories are different environments" For GitOps, Google recommends: Use folders for variants of the configuration instead of branches. With folders, you can use the tree command to see variants. For example, with branches, you can't tell if the delta between a prod and stage branch is an upcoming change in configuration or a permanent difference between what stage and prod should look like. https://cloud.google.com/anthos-config-management/docs/concepts/gitops-best-practices#use-folders "GKE Infrastructure (Anthos Config Management Kustomize manifests) repository is shared: different overlay directories are different environments" https://cloud.google.com/anthos-config-management/docs/tutorials/multiple-environments-config-sync#repository_architecture

this is the logial folder structure when dealing with multiple environments of tf, gke creating folders for separate environments, creating branches for releases

https://cloud.google.com/anthos-config-management/docs/concepts/gitops-best-practices#use-folders

I agree with @YushiSato, Terraform and Kustomize would be best practice to represent environments by a directory. https://cloud.google.com/anthos-config-management/docs/tutorials/multiple-environments-config-sync#repository_architecture

Choose B Cloud Infrastructure (Terraform) repository is shared: Allows you to manage the IaC for different env same repo, with different directories representing different env. This makes it easy to maintain and update common IaC across env. GKE Infrastructure (Anthos Config Management Kustomize manifests) repositories are separated: Each env GKE configuration is kept in a separate repo, using different branches for different env. This separation ensures that the GKE configurations for different env are distinct and can be managed independently. Application (app source code) repositories are separated: Each application has its own repo, and different branches can be used for different features or env. This separation allows application owners to manage their code independently and follow GitOps principles for application deployment.

I think A is correct. In both Terraform and Kustomize, it would be common to represent the environment by a directory.

Not sure, but I think it's better option.

It is recommended to use kustomize+ACM to manage multi environments using overlay+share-repo approach hence this narrows down to be either A or C. https://cloud.google.com/anthos-config-management/docs/tutorials/multiple-environments-config-sync#repository_architecture For app repo it should be shared therefore C is the right answer.