Why resource hierarchy matters in GCP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Resource Hierarchy Impact on Permissions

In Google Cloud, resources are organized in a hierarchy: Organization > Folder > Project > Resources. If you assign a role at the Folder level, what happens to the permissions on projects inside that folder?

A Permissions assigned at the Folder level only apply to the folder itself, not to projects inside it.

B Permissions assigned at the Folder level override any permissions set at the Organization level.

C Permissions assigned at the Folder level apply only to projects created after the assignment, not existing projects.

D Permissions assigned at the Folder level automatically apply to all projects and resources inside that folder.

💡 Hint

Think about how inheritance works in a family tree.

In Google Cloud, permissions set at a higher level in the resource hierarchy automatically apply to all resources below it. So, roles assigned at the Folder level apply to all projects and resources inside that folder.

❓ Architecture

intermediate

Choosing Resource Hierarchy for Billing and Access Control

You want to separate billing and access control for two departments in your company using Google Cloud. Which resource hierarchy setup best supports this goal?

A Create one Organization, then create two Folders—one for each department—and place projects under each folder accordingly.

B Create separate Organizations for each department and place projects directly under each Organization.

C Create all projects directly under the Organization without folders and use labels to separate departments.

D Create one Folder for all projects and assign billing accounts per project.

💡 Hint

Think about grouping projects logically for billing and access.

Using folders under a single Organization allows you to group projects by department. This makes it easier to assign billing accounts and access controls at the folder level, which then apply to all projects inside.

❓ security

advanced

Effect of Removing a Folder on Resource Access

If you delete a Folder in Google Cloud that contains several projects, what happens to the access permissions and resources inside those projects?

A The projects move up one level to the Organization, and their access permissions remain intact or inherited from the Organization.

B The projects inside the folder are deleted along with the folder, and all access permissions are removed.

C The projects become orphaned with no access permissions until manually reassigned.

D The projects remain inside the folder but lose all inherited permissions from the folder.

💡 Hint

Consider what happens to children when their parent is removed in a hierarchy.

When a folder is deleted, its projects move up to the Organization level. They retain their access permissions, either directly assigned or inherited from the Organization.

❓ service_behavior

advanced

Impact of Resource Hierarchy on Service Quotas

How does Google Cloud apply service quotas when resources are organized in a hierarchy?

A Service quotas are applied at the Organization level and automatically divided among projects.

B Service quotas are applied only at the project level, regardless of hierarchy.

C Service quotas are applied individually to each resource, ignoring project or folder grouping.

D Service quotas can be shared and aggregated across projects within the same folder.

💡 Hint

Think about how limits are usually set per isolated unit.

In Google Cloud, service quotas are set and enforced at the project level. The resource hierarchy does not aggregate or share quotas across projects or folders.

✅ Best Practice

expert

Best Practice for Organizing Resources to Minimize Risk

You want to design a Google Cloud resource hierarchy that minimizes the risk of accidental permission changes affecting critical projects. Which approach is best?

A Place all projects in one folder and assign permissions at the project level only.

B Assign all permissions at the Organization level to simplify management, without using folders.

C Place critical projects in a separate folder with strict permissions, and assign broader permissions only at the Organization level.

D Use folders for non-critical projects and place critical projects directly under the Organization with no folders.

💡 Hint

Think about isolating sensitive resources to control access tightly.

Separating critical projects into their own folder with strict permissions helps isolate them from broader permissions assigned at higher levels. This reduces risk of accidental permission changes affecting critical resources.