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


Contribute your Thoughts:

Pansy
3 months ago
I like option D because it designates the Organization for production projects only, minimizing the risk of developers modifying them.
upvoted 0 times
...
Adria
3 months ago
But with option C, you can create separate folders for development and production, providing an organized structure.
upvoted 0 times
...
Gilma
3 months ago
I prefer option B because it allows for a clear separation of production projects by creating a 'Production' folder.
upvoted 0 times
...
Adria
4 months ago
I think option A is the best choice because it involves creating a new Organization to separate production projects.
upvoted 0 times
...
Tom
4 months ago
I like option D because it designates the Organization for production projects only, minimizing the risk of developers modifying them.
upvoted 0 times
...
Fredric
5 months ago
But with option C, you can create separate folders for development and production, providing an organized structure.
upvoted 0 times
...
Daniel
5 months ago
I prefer option B because it allows for a clear separation of production projects by creating a 'Production' folder.
upvoted 0 times
...
Fredric
5 months ago
I think option A is the best choice because it involves creating a new Organization to separate production projects.
upvoted 0 times
...
Malcolm
6 months ago
I agree, the separate account and Organization option seems a bit overkill. The folder approach seems like a much more elegant solution.
upvoted 0 times
...
Lelia
6 months ago
Haha, can you imagine if we went with option A and had to manage two separate Google Workspace accounts? That would be a nightmare!
upvoted 0 times
...
Lelia
6 months ago
I agree, option C is the most elegant solution. It allows us to delegate project creation to the developers, while still maintaining control over the production environment.
upvoted 0 times
...
Katlyn
6 months 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 months 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
6 months 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
6 months 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
Ernie
4 months ago
B
upvoted 0 times
...
Aide
5 months ago
B
upvoted 0 times
...
Marguerita
5 months ago
A
upvoted 0 times
...
Daren
5 months ago
A
upvoted 0 times
...
...
Raylene
6 months 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
6 months 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 months 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
Hildegarde
5 months ago
A) Yeah, option A or B seem like the safest and most efficient ways to design the Organization structure for our needs.
upvoted 0 times
...
Fredric
5 months ago
D) I'm not sure if option D is the best choice, as it creates projects outside of the Organization which might cause security concerns.
upvoted 0 times
...
Xenia
5 months ago
B) Setting policies for all projects on the Organization and additional policies for the 'Production' folder could be a good way to ensure security.
upvoted 0 times
...
Bok
6 months ago
C) Option C also separates projects effectively and grants developers the necessary IAM role for project creation.
upvoted 0 times
...
Ciara
6 months ago
A) I agree, having separate folders for 'Development' and 'Production' would make it easier to manage policies.
upvoted 0 times
...
Rosendo
6 months ago
B) Option B seems like a good choice as it separates the 'Production' projects from the rest and still allows for project creation by developers.
upvoted 0 times
...
Onita
6 months ago
A) Sounds like option A would work well for our situation. It allows developers to create projects but also centralizes the policy management.
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