GOOGLE CLOUD RESOURCE HIERARCHY Q&A

GOOGLE CLOUD RESOURCE
HIERARCHY Q&A
Resource manager tool - ANSWER-Gather list of projects, create/update/delete/recover
projects, access through RPC and REST API

Folder - ANSWER-let you assign policies to resources at a level of granularity you
choose

you can use folders to group projects under an organization in a hierarchy EG (different
folder per department)

apply one policy for a whole downline instead of each project

Organization node - ANSWER-designate admins, project creator role (they spend
money).
Level 1 - ANSWER-Resources

Level 2 - ANSWER-Projects

Level 3 - ANSWER-Folder

Level 4 - ANSWER-Organization Node

Resources - ANSWER-VM, Cloud storage buckets, tables of query, google cloud

Hierarchy order - ANSWER-Resources are organized into projects. Projects are
organized into folders/subfolders, organization node encompasses everything in your
organization

Policies in google cloud - ANSWER-Can be defined at project, folder, and node level.
Some can be applied to resources.

Policies are inherited downward (apply to folder and everything beneath gets the same
policy)

Projects - ANSWER-Enable services under google cloud:
1 projects are separate entities under the organization node
2 projects hold resources, each of which belongs to one project
3 projects can have different owners and users because they're billed and managed
separately