Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional-Cloud-Architect Topic 10 Question 79 Discussion

Actual exam question for Google's Google Cloud Architect Professional exam
Question #: 79
Topic #: 10
[All Google Cloud Architect Professional Questions]

Your company has a Google Workspace account and Google Cloud Organization Some developers in the company have created Google Cloud projects outside of the Google Cloud Organization

You want to create an Organization structure that allows developers to create projects, but prevents them from modifying production projects You want to manage policies for all projects centrally and be able to set more restrictive policies for production projects

You want to minimize disruption to users and developers when business needs change in the future You want to follow Google-recommended practices How should you design the Organization structure?

Show Suggested Answer Hide Answer
Suggested Answer: C

This option can help create an organization structure that allows developers to create projects, but prevents them from modifying production projects. Folders are containers for projects and other folders within Google Cloud organizations. Folders allow resources to be structured hierarchically and inherit policies from their parent resources. By creating folders under the organization resource named ''Development'' and ''Production'', you can organize your projects by environment and apply different policies to them. By granting all developers the Project Creator IAM role on the ''Development'' folder, you can allow them to create projects under that folder, but not under the ''Production'' folder. By moving the developer projects into the ''Development'' folder, you can ensure that they are subject to the policies set on that folder. By setting the policies for all projects on the organization, you can manage policies centrally and efficiently. By additionally setting the production policies on the ''Production'' folder, you can enforce more restrictive policies for production projects and prevent developers from modifying them. The other options are not optimal for this scenario, because they either create a second Google Workspace account and organization, which increases complexity and cost (A), or do not use folders to organize projects by environment, which makes it harder to manage policies and permissions (B, D). Reference:

https://cloud.google.com/resource-manager/docs/creating-managing-folders

https://cloud.google.com/architecture/framework/system-design


Comments

Katlyn
5 hours ago
Hmm, I'm not sure I like the idea of having a separate Google Workspace account and Organization just for the developer projects. That seems like it could be more trouble than it's worth.
upvoted 0 times
...
Katina
6 hours ago
I think option C is the way to go. Creating separate folders for development and production projects, and then setting the appropriate policies on each, seems like the cleanest solution.
upvoted 0 times
...
Thad
1 days ago
Hmm, this is an interesting question. We need to find a way to manage the projects and policies centrally, while still allowing developers to create new projects without disrupting the production environment.
upvoted 0 times
...
Carlee
1 days ago
You're right, we need to be careful about who has that kind of access. Maybe we could limit the Project Creator role to a specific group of trusted developers instead.
upvoted 0 times
...
Raylene
2 days ago
Yeah, the folders idea sounds good. But I'm not sure about granting all developers the Project Creator role on the Organization. That seems like it could lead to some security issues down the line.
upvoted 0 times
...
Earlean
4 days ago
I like the idea of using folders to separate the production and development projects. That way, we can set more restrictive policies for the production projects without disrupting the developers.
upvoted 0 times
...
Gary
6 days ago
Hmm, this seems like a tricky question. We need to find a way to manage production and development projects separately, while still allowing developers to create projects as needed.
upvoted 0 times
...

Save Cancel