Explanation:
Options B, C, and D are incorrect because assigning permissions at the Project, Organization, or folder level does not allow for granular access control per repository within a Project. Option A is correct because it enables the assignment of different roles to different teams for each repository, providing the flexibility and specificity required for managing access effectively. Reference: Google Cloud Source Repositories Documentation
A company is planning to utilize Google Cloud Platform (GCP) for the development and deployment of their applications. They have already established an organization, folders, and projects. Their goal is to set up multiple Cloud Source Repositories (CSR) within a single Project, with different teams requiring varied access levels to these CSRs. What is the most effective method to manage access to the CSRs for these different teams?
A
Assign the permissions for the different teams at the repository level
B
Assign the permissions for the different teams at the Project level
C
Assign the permissions for the different teams at the Organization level
D
Assign the permissions for the different teams at the folder level
No comments yet.