Cloud Digital Leader How Google Cloud Resources Are Managed Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Organization node

  Why this is correct

  The organization node is the top-level (root) node in the Google Cloud resource hierarchy. It represents the entire enterprise and is typically created automatically when a Google Cloud account is established or a domain is claimed. All other resources—folders, projects, and billing associations—are ultimately attached beneath it, allowing organization-wide IAM policies, organization policies, and access governance to be applied uniformly.

• ✗

  Billing account

  Why it's wrong here

  A billing account is a separate financial entity used to track and pay for cloud usage, linked to one or more projects. It is not part of the resource hierarchy and does not contain or organize resources. Billing accounts sit outside the hierarchy entirely, whereas the organization node is the true root within the hierarchy.

• ✗

  Folder

  Why it's wrong here

  Folders are intermediate grouping nodes within the resource hierarchy, used to organize projects into departments, teams, or applications. They provide a level of hierarchy beneath the organization node and allow policy inheritance to be scoped to a group of projects. Because folders are always contained within the organization node, they cannot be the root.

• ✗

  Project

  Why it's wrong here

  Projects are the leaf-level containers in the resource hierarchy, directly holding resources such as compute instances, storage buckets, and APIs. Every project belongs to a folder or, if created without a folder, to the organization node itself. As the lowest level of the hierarchy, a project is not a root node but rather a descendant that inherits policies from above.

Go deeper

Related to this question