Valid Professional-Cloud-DevOps-Engineer Dumps shared by EduDump.com for Helping Passing Professional-Cloud-DevOps-Engineer Exam! EduDump.com now offer the newest Professional-Cloud-DevOps-Engineer exam dumps, the EduDump.com Professional-Cloud-DevOps-Engineer exam questions have been updated and answers have been corrected get the newest EduDump.com Professional-Cloud-DevOps-Engineer dumps with Test Engine here:
You are designing a system with three different environments: development, quality assurance (QA), and production. Each environment will be deployed with Terraform and has a Google Kubernetes Engine Enterprise (GKE Enterprise) cluster created so that application teams can deploy their applications. Config Sync will be used and templated to deploy infrastructure-level resources in each GKE Enterprise cluster. All users (for example, infrastructure operators and application owners) will use GitOps. How should you structure your source control repositories for both infrastructure as code (IaC) and application code?
Correct Answer: A
Comprehensive and Detailed Explanation: To follow GitOps best practices and Google Cloud's recommended repository structure for Terraform (IaC), Config Sync, and application code, we should use a shared repository for Terraform and Config Sync while keeping application repositories separate. Cloud Infrastructure (Terraform) repository is shared # This allows infrastructure teams to manage all environments in a single repository with different directories per environment (dev, QA, production). This is the standard approach to structuring Terraform repositories. GKE Enterprise Infrastructure (Config Sync) repository is shared # Using Kustomize overlays per environment (instead of separate repositories) aligns with Config Sync's best practices and makes managing configurations easier. Application repositories are separated, using different branches for features # This allows application teams to follow the Git branching model (feature branches, main branch, release branches, etc.) without affecting infrastructure. #Official Reference: Config Sync Best Practices Terraform Structure Best Practices GitOps Best Practices