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.
Here's why:
Projects are the fundamental unit of resource isolation and management in Google Cloud. Using one project per team provides:
Strong Isolation: Resources in different projects are completely isolated from each other. This reduces the risk of accidental interference between teams' work.
Separate Billing: Each project has its own billing, providing clear cost visibility per team. This makes it easy to track spending and allocate budgets.
Simplified IAM: Access control is managed at the project level. This makes it easy to grant appropriate permissions to each team without affecting other teams' resources.
Flexibility: As teams change or new teams are formed, creating or deleting projects is a straightforward process.
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.
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, 7 months agogeeroylenkins
2 years agoptoul74
Highly Voted 2 years ago2dc3345
Most Recent 3 days, 12 hours agonsjag_1
1 month, 4 weeks agovsannid
3 months, 2 weeks agobob_chd
4 months, 2 weeks agoAntoineMo
5 months agoViztvm
5 months, 2 weeks agorobi11
6 months agoNishantkumar
6 months, 2 weeks agoMarvinB123
9 months agojoe03
10 months ago4a98421
1 year, 1 month agosivakarthick16
1 year, 4 months agosanidh
1 year, 5 months agochai_gpt
1 year, 5 months ago__rajan__
1 year, 6 months ago