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 1 Question 89 Discussion

Actual exam question for Google's Google Cloud Architect Professional exam
Question #: 89
Topic #: 1
[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


Contribute your Thoughts:

Earleen
1 months ago
I personally prefer option D. It designates the Organization for production projects only and keeps development projects outside of the Organization.
upvoted 0 times
...
Yen
1 months ago
That's a good point. Option C does provide a clear separation between development and production projects. It could make policy management easier.
upvoted 0 times
...
Graciela
2 months ago
I disagree, I believe option C is better. It separates development and production projects into different folders for better organization.
upvoted 0 times
...
Harrison
2 months ago
Option B seems a bit too simple. I think the folder structure in Option C gives you a bit more flexibility to grow and adapt in the future.
upvoted 0 times
Rhea
1 months ago
Yeah, having separate folders for development and production projects can help with organization and management.
upvoted 0 times
...
Leonora
1 months ago
I agree, Option C does seem to provide more flexibility for future changes.
upvoted 0 times
...
...
Marcos
2 months ago
Haha, Option D is just asking for trouble. Trying to keep developers out of the production projects? Good luck with that, my friend.
upvoted 0 times
...
Yen
2 months ago
I think option B is the best choice. It allows us to create a folder for production projects while still giving developers the ability to create projects.
upvoted 0 times
...
Keena
2 months ago
I like how Option C uses the folder structure to keep things organized. That's a nice, clean way to handle the different project types.
upvoted 0 times
Charlene
1 months ago
Yeah, it's a simple and effective way to ensure policies are set correctly for each type of project.
upvoted 0 times
...
Tina
2 months ago
I agree, having separate folders for development and production projects makes it easier to manage.
upvoted 0 times
...
Dylan
2 months ago
Option C does seem like a good way to keep things organized.
upvoted 0 times
...
...
Barney
2 months ago
Option C looks like the best choice here. Separating the development and production projects into different folders will make it easier to manage the policies for each environment.
upvoted 0 times
Cristina
2 months ago
Definitely, it's a good balance between control and flexibility for the developers.
upvoted 0 times
...
Margurite
2 months ago
It also allows us to set more restrictive policies for the production projects while still giving developers the freedom to create projects in the development folder.
upvoted 0 times
...
Maxima
2 months ago
I agree, having separate folders for development and production projects will help keep things organized.
upvoted 0 times
...
Silva
2 months ago
Option C looks like the best choice here. Separating the development and production projects into different folders will make it easier to manage the policies for each environment.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77