
Answer-first summary for fast verification
Answer: Create a single G Suite account to manage users with each stage of each application in its own project
The question requires a structure that enforces a least privilege model with separation of duties between production and development resources. Option C aligns with Google Cloud's best practices, as cited in the community discussion and official documentation (e.g., 'A general recommendation is to have one project per application per environment'). This approach isolates environments, preventing accidental impacts (e.g., development changes affecting production) and enabling granular access control (e.g., restricting production access to authorized personnel). Options A and B are suboptimal because using multiple G Suite accounts is unnecessary and complicates user management; a single account with IAM roles suffices. Option D is less suitable as it groups all development/test/staging environments into one project, reducing isolation and increasing the risk of cross-environment interference. The community consensus strongly supports C, with high upvotes and references to Google's best practices.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As a Google Professional Cloud Architect, what domain and project structure would you recommend to enforce a least privilege model with separation of duties for administering production and development resources at JencoMart?
A
Create two G Suite accounts to manage users: one for development/test/staging and one for production. Each account should contain one project for every application
B
Create two G Suite accounts to manage users: one with a single project for all development applications and one with a single project for all production applications
C
Create a single G Suite account to manage users with each stage of each application in its own project
D
Create a single G Suite account to manage users with one project for the development/test/staging environment and one project for the production environment
No comments yet.