Your company needs to segment Google Cloud resources used by each team from the others. The teams' efforts are changing frequently, and you need to reduce operational risk and maintain cost visibility. Which approach does Google recommend?
A.
One project per team.
B.
One organization per team.
C.
One project that contains all of each team's resources.
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
In a company of 80,000, you might have 8,000 teams. Maybe 16,000. You want a top level folder for EACH? You don't need a TOP level folder for each. Maybe 1 per BU, then 1 per BU Department, then 1 per BU Department Division, then 1 per BU Department Division Team, etc. Nested folders, like Russian Dolls.
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.
One project per team.
This method provides clear boundaries between teams’ resources, simplifies billing processes, enhances security through tailored IAM policies, and allows for easy adjustments as team structures evolve.
A. One project per team.
Projects in Google Cloud provide a natural boundary for resources, permissions, and billing. Each project can be managed independently, which helps in isolating resources and controlling access.
This approach allows for clear cost tracking and visibility, as each team's usage and expenses can be monitored separately.
It also reduces operational risk by containing any changes or issues within a specific project, preventing them from affecting other teams.
Using one project per team aligns with Google's best practices for resource management and helps maintain a structured and manageable cloud environment
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.
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.
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.
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
mamitos
Highly Voted 2 years, 2 months agogeeroylenkins
1 year, 8 months agoptoul74
Highly Voted 1 year, 7 months agobob_chd
Most Recent 1 week, 1 day agoAntoineMo
2 weeks, 6 days agoViztvm
1 month agorobi11
1 month, 2 weeks agoNishantkumar
2 months agoMarvinB123
4 months, 3 weeks agojoe03
5 months, 3 weeks ago4a98421
9 months, 2 weeks agosivakarthick16
12 months agosanidh
1 year agochai_gpt
1 year, 1 month ago__rajan__
1 year, 2 months agomdsarfraz69
1 year, 3 months agoLufly
1 year, 3 months agocookieMr
1 year, 6 months ago