Google Professional Cloud Security Engineer Question 153
Single answerGoogle Cloud PlatformYour organization uses Google Cloud and has multiple projects with different teams managing each. To simplify permission management, you decide to use Google Groups. You need to ensure that team-specific permissions are properly applied and maintained with minimal administrative overhead. What is the best approach to manage permissions using groups in this scenario?
- A
Create a Google Group for each team, assign roles to the group at the project level, and add team members to the respective groups.
- B
Assign roles directly to individual users for each project to ensure precise control over permissions.
- C
Use Google Groups to create a single group for all team members across the organization and assign global roles to the group.
- D
Create a Google Group for each team, assign roles to the group at the resource level (e.g., buckets, BigQuery datasets) instead of the project level.
Show answer and explanation
Correct answer: A
Explanation
Using Google Groups to manage permissions at the project level ensures that access control is streamlined and aligned with organizational policies. When members are added or removed from a group, their permissions are automatically updated without requiring manual role adjustments. Assigning roles at the project level also provides a balance between granularity and simplicity, making it easier to maintain consistent security policies across teams.
- A. Correct.
This is the correct approach as it simplifies permission management. By assigning roles to groups at the project level, you reduce administrative overhead and ensure that permissions for team members are managed collectively through their group membership.
- B. Incorrect.
Assigning roles directly to individual users can become unmanageable and error-prone, especially in large organizations, as it requires manual updates whenever team members change.
- C. Incorrect.
Using a single group for the entire organization defeats the purpose of team-specific permission management. It can lead to over-provisioning of access and security risks.
- D. Incorrect.
Assigning roles at the resource level rather than the project level can make permissions harder to maintain and might not align with the principle of least privilege if the roles are too broad.