What is the main purpose of using folders in Google Cloud Platform's resource hierarchy?
Think about how folders help organize and manage multiple projects.
Folders in GCP are used to group projects so that you can apply policies and permissions to all projects inside the folder at once. They do not store data or replace projects.
You have three departments: Sales, Engineering, and Marketing. Each has multiple projects. Which folder structure best supports applying department-specific policies?
Consider how to apply policies easily to all projects in a department.
Creating one folder per department allows you to apply policies to all projects in that department easily. Other options do not group projects by department effectively.
If you assign an IAM role to a folder, what happens to the projects inside that folder?
Think about how permissions flow down in GCP resource hierarchy.
IAM roles assigned to a folder are inherited by all projects inside it, allowing centralized permission management.
What happens to projects inside a folder if the folder is deleted in GCP?
Consider how GCP handles resource hierarchy changes.
When a folder is deleted, its projects do not get deleted. Instead, they move up one level in the resource hierarchy, usually directly under the organization.
You want to separate billing and access control for multiple teams working on different projects. Which folder design best supports this?
Think about how folders help organize projects for both billing and access control.
Folders per team allow you to manage access control easily and assign billing accounts at the project level inside those folders, supporting separation of billing and permissions.