CLOUD-DIGITAL-LEADER · Question #82
You are consulting for a client who is migrating to Google Cloud. They presently have a matrix or- ganization. Their IT environments were managed around projects. Each team had multiple projects…
The correct answer is A. On Google Cloud, create a folder corresponding to each team. Under that, there could be projects. Folders for a related group of projects are the recommended approach. -> A flat structure under the organization node is possible on Google Cloud, but it is not recommended. It becomes tougher to manage. -> Projects cannot have sub-projects; there can only be resources within…
Question
You are consulting for a client who is migrating to Google Cloud. They presently have a matrix or- ganization. Their IT environments were managed around projects. Each team had multiple projects. All the projects had a flat structure under the company. What would you advise them when plan-ning for the move?
Options
- AOn Google Cloud, create a folder corresponding to each team. Under that, there could be projects
- BIn terms of not disturbing the project developers and testers, advise them that the strategic
- CSince a Project could spawn other sub-Projects, on Google Cloud it is better to as-sign a folder
- DThe flat structure is what is currently used in IT organizations, and this can be used as-is which
How the community answered
(31 responses)- A71% (22)
- B16% (5)
- C3% (1)
- D10% (3)
Explanation
Folders for a related group of projects are the recommended approach. -> A flat structure under the organization node is possible on Google Cloud, but it is not recommended. It becomes tougher to manage. -> Projects cannot have sub-projects; there can only be resources within Projects. https://cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy
Topics
Community Discussion
No community discussion yet for this question.