Projects as organizational units in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Project Hierarchy in GCP

Which statement best describes the role of a Project in Google Cloud Platform's organizational structure?

A A Project is a top-level container that can hold multiple organizations.

B A Project is an organizational unit that groups resources and belongs to an organization or no organization.

C A Project is a user account that manages billing and permissions across organizations.

D A Project is a billing account that controls access to multiple organizations.

💡 Hint

Think about where projects fit in the hierarchy between organizations and resources.

In GCP, a Project is a container for resources and belongs under an Organization or can exist without one. It is not a top-level container nor a user or billing account.

❓ Architecture

intermediate

Project Placement in GCP Hierarchy

You have an Organization in GCP and want to create a new Project for a team. Where should this Project be placed to follow best practices?

A Under the Billing Account node.

B Directly under the Organization node as a child.

C Under a Folder that groups multiple related Projects.

D As a sibling to the Organization node.

💡 Hint

Consider how folders help organize projects within an organization.

Folders are used to group related projects under an organization for better management. Projects cannot be siblings to organizations or placed under billing accounts.

❓ security

advanced

IAM Permissions Scope in Projects

Which statement correctly describes how IAM permissions apply within a GCP Project?

A IAM permissions granted at the Project level apply only to resources created after the permission is granted.

B IAM permissions granted at the Project level automatically apply to all Projects in the Organization.

C IAM permissions cannot be set at the Project level; they must be set on individual resources only.

D IAM permissions granted at the Project level apply to all resources within that Project, including existing and future resources.

💡 Hint

Think about inheritance of permissions within a project.

Permissions set at the Project level apply to all resources within that project, both existing and future. Permissions do not cascade across projects automatically.

✅ Best Practice

advanced

Billing Account Association with Projects

What is the best practice for associating billing accounts with Projects in GCP?

A Associate Projects with billing accounts as needed; multiple Projects can share one billing account for consolidated billing.

B Associate each Project with its own billing account to isolate costs completely.

C Associate one billing account per Organization and share it with all Projects automatically.

D Billing accounts are not linked to Projects; billing is managed at the user level.

💡 Hint

Consider how billing accounts and projects relate for cost management.

Multiple projects can share a single billing account to consolidate billing, but projects can also have separate billing accounts if isolation is needed.

❓ service_behavior

expert

Impact of Deleting a Project in GCP

What happens to the resources and services within a GCP Project when the Project is deleted?

A The Project and its resources enter a 30-day soft-delete period during which recovery is possible before permanent deletion.

B Only the Project metadata is deleted; resources continue running and billing persists.

C All resources are immediately deleted and cannot be recovered.

D Resources are transferred automatically to the Organization's default Project.

💡 Hint

Think about Google's safety measures for accidental deletions.

When a Project is deleted, it enters a 30-day soft-delete period allowing recovery. After this, resources and the project are permanently deleted.