Exam Cloud Digital Leader topic 1 question 62 discussion

It should be D, a top-level folder for each team give the ability to have multiple projects(I guess here goes the "teams efforts change frequently) and also cost is closely being watched and separated by Team->Team_Project. I hate GCP, so many poorly worded and vague questions...shame

Have a look at this image https://cloud.google.com/static/resource-manager/img/cloud-hierarchy.svg?dcb_=0.14515370615705625. Then, the correct answer is obviously D.

Even though Project and Folder are suitable, Folder is more suitable for team control as there can be multiple projects live Dev, QA, PROD for each team.

A is the correct answer...

Correct Answer: A. One project per team. Explanation: One project per team is the recommended approach in Google Cloud for resource segmentation. This method allows each team to have its own isolated environment, making it easier to manage permissions, monitor costs, and enforce policies specific to that team. By using separate projects, you can clearly delineate resources and costs associated with each team's activities, which enhances visibility and reduces operational risk as teams can operate independently without affecting each other's resources.

A is correct.

Answer should be 1 top-level folder per team so that they can create 1 project per environment which is also best practice.

A is correct, there is only 1 top level for Organization, then folders as per department/team and then projects for each department/team.

D is correct

................................

D is correct

D. One top-level folder per team. Folders in Google Cloud provide a way to organize and manage resources hierarchically, making it easier to allocate resources to specific teams, manage access control, and maintain cost visibility. Each top-level folder can represent a different team, and you can create a hierarchy of folders to further organize resources as needed.

A is correct

Here are some reasons why using one project per team is not a good idea for resource segmentation: Inflexibility: It would prevent teams from changing their resources frequently. If a team needs to add or remove resources, they would need to create a new project or delete the old project. This can be time-consuming and disruptive. Cost: It would be more expensive to manage multiple projects. Each project has its own set of costs, such as storage costs, compute costs, and networking costs. This can add up quickly if you have a lot of projects. Complexity: It would be more complex to manage multiple projects. You would need to keep track of the resources in each project, as well as the costs of each project. This can be difficult to do, especially if you have a lot of projects.

One project per team approach offers clear separation and isolation of resources for each team, providing enhanced security, compliance, and operational control. Each team can have its own dedicated project, allowing them to independently manage their resources, control access permissions, and maintain cost visibility. Changes made by one team will not directly impact the resources of other teams, reducing operational risks and providing a more stable environment.

Option D, "One top-level folder per team" is a possible approach to organizing Google Cloud resources, but it is not the recommended approach for the scenario described in the question. Folders are a way to organize projects and resources hierarchically within a Google Cloud organization. They are useful for creating custom organizational structures, managing access controls, and delegating administrative responsibilities. However, if the goal is to separate resources used by each team from the others and maintain cost visibility, organizing resources into one project per team or one organization per team would provide more clear separation and better cost tracking. Therefore, option A, "One project per team," is the recommended approach for this scenario.

It should be 'A' as it says "segment Google Cloud resources". if we follow the best practices of resource hierarchy Org->folders-subfolder->Project->resources. so the idea here is to create two project for each team to segment the resources with clear visibility