Exam Professional Cloud Developer topic 1 question 270 discussion

a, however from june 17 2024 onwards CSR is no longer available for new clients.

C and D (GitHub repository, mirrored to CSR): While GitHub offers feature-based development workflows, mirroring to CSR introduces an additional step and potential delay in the development process. It also doesn't provide the same level of native IAM integration as using CSR directly.

I will go for A instead of C because it's more simple and straightforward. There isn't a requirement to have PR's or something like that to choose to have GitHub.

I choose A. Where does the GitHub repository requirement come from? The security team uses IAM for user accesses and we only need to create a version control system that can integrate with their processes. IAM can't control who is pushing stuff in GitHub and with options C or D it will end up in CSR regardless. Fast release cycles and frequent merges to the main branch to minimize merge conflicts -> trunk-based development.

"You want your solution to support fast release cycles and frequent merges to your main branch to minimize merge conflicts." The requirement for fast release cycles and frequent merges with minimal merge conflicts aligns well with trunk-based development. In trunk-based development, developers work in short-lived branches and merge their changes frequently into the main branch, which helps in reducing merge conflicts and supports a more rapid and continuous release cycle.

C. using an external git repository as Github or Bitbucket synced with Cloud Repositories is a best practice, as it provides with a lot more features as PRs and branch permissions. Trunk or master development is okay in this case as is a small project with fast development. For more large projects, larger teams is better to use a feature development as GitFlow

GitHub Repository: GitHub is a popular and powerful platform for version control. It supports a wide range of development workflows and integrates well with various CI/CD tools, making it suitable for fast release cycles. Mirroring to Cloud Source Repositories: By mirroring the GitHub repository to Google Cloud Source Repositories, you can leverage Google Cloud's IAM features for access control and security. This integration allows your security team to track and manage user access effectively within the Google Cloud environment. Trunk-Based Development: This development methodology involves developers merging their changes into the main branch frequently. It's well-suited for fast-paced development environments, as it minimizes the duration of branches and reduces the likelihood of significant merge conflicts.