Free Google Cloud-Digital-Leader Actual Exam Questions - Question 1 Discussion
segregated from one another. Each department has several environments of its own: development,
testing, and production. Which strategy should your organization choose?
B. Projects are the real resource containers, and folders are just for grouping. Having folders by department and projects by environment keeps access control simple and resource boundaries clear.
B seems right since folders are meant to group projects, not the other way around. This keeps environment projects isolated but still under the right department umbrella.
Option B also stands out because projects are the actual containers for resources, and folders are meant to organize those projects. Having a folder per department and a project per environment fits well with Google Cloud’s best practices for separation. Plus, managing IAM and billing per project is straightforward this way. Options C and D overcomplicate things by introducing multiple Cloud Identity domains, which isn’t necessary and adds overhead. Option A flips the hierarchy, which doesn’t align with how folders and projects are meant to be structured. So, B’s structure just makes the most
B/D? D is way too much overhead with separate Cloud Identity domains for environments. B makes more sense since folders organize projects, and projects hold resources, so each environment within a department stays nicely separated.
A/C? A feels off since folders usually group projects, not the other way around. C seems complicated with multiple Cloud Identity domains, which isn’t standard for department splits. B still looks cleaner overall.
It’s B for me. Folders are meant to group projects, so having a folder per department and projects per environment keeps everything structured and easy to manage. Projects are the actual resource containers, so environments should be separate projects. Also, options C and D don’t fit because Cloud Identity domains are for different organizations, not for segregating environments or departments within the same org. A flips the hierarchy wrongly—projects can’t contain folders, so A doesn’t make sense either. B is the cleanest way to logically separate both departments and their environments.
Makes sense to go with B, since folders help organize projects neatly by environment within each department. Plus, Cloud Identity domains (like in C and D) are usually for separate organizations, so those options seem off here. Also, A’s idea of folders inside projects isn’t how Google Cloud structures things—projects are the main containers. So B fits best for clear segregation and management.
It’s B, folders better group projects by environment under each department.
B imo, but does the question specify any constraints on billing or IAM setup?