Google Professional Cloud Security Engineer Question 167
Single answerGoogle Cloud PlatformYour company has recently adopted Google Cloud and plans to use multiple projects for isolated workloads. You want to ensure that all resources across these projects comply with centralized security policies, while also allowing teams to manage their individual projects. How should you design the resource hierarchy to meet these requirements?
- A
Create a single project for all workloads and apply security policies at the project level.
- B
Use folders under the organization node to group related projects and apply security policies at the folder level.
- C
Apply security policies directly to each individual project without using folders.
- D
Do not create an organization node and manage policies at the project level for each workload.
Show answer and explanation
Correct answer: B
Explanation
The recommended approach in Google Cloud's resource hierarchy is to use folders under the organization node to group related projects. This design allows for centralized control and enforcement of security policies at the folder level, while still providing flexibility for individual teams to manage their projects. This approach is scalable, aligns with best practices, and ensures compliance with organizational security requirements.
- A. Incorrect.
This option does not allow for isolated workloads or hierarchical policy enforcement, making it difficult to manage resources and comply with centralized security policies.
- B. Correct.
Using folders under the organization node allows logical grouping of projects and enables centralized security policy enforcement at the folder level, while still allowing teams to manage their individual projects.
- C. Incorrect.
Applying security policies directly to individual projects does not take advantage of Google Cloud's resource hierarchy for centralized and scalable management, making it less effective in enforcing organization-wide security policies.
- D. Incorrect.
Not creating an organization node results in a fragmented resource setup with no centralized control, which is not recommended for enterprises managing multiple projects.