PROFESSIONAL-CLOUD-ARCHITECT · Question #67
Case Study: 3 - JencoMart Case Study Company Overview JencoMart is a global retailer with over 10,000 stores in 16 countries. The stores carry a range of goods, such as groceries, tires, and…
The correct answer is C. Create a single G Suite account to manage users with each stage of each application in its own. https://cloud.google.com/resource-manager/docs/creating-managing-folders Refer to the diagram on top, different envs are created at the project level. https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations "A general recommendation is to have one…
Question
Options
- ACreate two G Suite accounts to manage users: one for development/test/staging and one for
- BCreate two G Suite accounts to manage users: one with a single project for all development
- CCreate a single G Suite account to manage users with each stage of each application in its own
- DCreate a single G Suite account to manage users with one project for the
How the community answered
(47 responses)- A4% (2)
- B6% (3)
- C77% (36)
- D13% (6)
Explanation
https://cloud.google.com/resource-manager/docs/creating-managing-folders Refer to the diagram on top, different envs are created at the project level. https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations "A general recommendation is to have one project per application per environment. For example, if you have two applications, "app1" and "app2", each with a development and production environment, you would have four projects: app1-dev, app1-prod, app2-dev, app2-prod. This isolates the environments from each other, so changes to the development project do not accidentally impact production, and gives you better access control, since you can (for example) grant all developers access to development projects but restrict production access to your CI/CD
Topics
Community Discussion
No community discussion yet for this question.