Examkin

Question

Difficulty: MediumManaging Cloud Projects and Resource Hierarchy

An organization is setting up a new Google Cloud environment from scratch. Arrange the following steps in the correct sequential order to establish the resource hierarchy and prepare a project for application workloads according to Google Cloud best practices.

  1. 1Provision the top-level Google Cloud Organization resource via Cloud Identity or Google Workspace.
  2. 2Create environment-specific Folders under the Organization node to isolate business workloads.
  3. 3Create a new Google Cloud Project inside the designated environment Folder.
  4. 4Link an active Billing Account to the newly created Google Cloud Project.
  5. 5Enable required Google Cloud Service APIs and grant least-privilege IAM roles to project users.

Answer

The correct sequence begins with provisioning the top-level Organization resource, followed by creating environment Folders beneath it, creating the Cloud Project inside the appropriate Folder, linking an active Billing Account to the Project, and finally enabling Cloud Service APIs and configuring IAM roles.
Google Cloud resources strictly follow a top-down dependency hierarchy: Organization -> Folder -> Project. Operational setup requires establishing the project container, attaching an active billing account, and then enabling project APIs and granting access permissions.

Step-by-Step Solution

1
Establish the root node of the resource hierarchy.
Provision the Google Cloud Organization resource via Cloud Identity.
The Organization resource is the top-level root node required for folder creation and centralized governance.
2
Create administrative groupings under the root node.
Create environment Folders under the Organization node.
Folders allow administrative isolation and inheritance of policy constraints for child projects.
3
Instantiate the resource container.
Create a Google Cloud Project within the designated Folder.
Projects are child elements of Folders and serve as the physical containers for GCP resources.
4
Attach billing capabilities to the project container.
Link an active Billing Account to the Cloud Project.
Google Cloud requires an active billing attachment before enabling APIs or creating paid billable resources.
5
Configure services and access controls.
Enable required APIs and grant least-privilege IAM permissions on the Project.
Service APIs must be explicitly enabled within a billing-enabled project container before deploying workload resources.

Key Concept

Google Cloud Resource Hierarchy Provisioning Order
Rate this question

Topics

Managing Cloud Projects and Resource Hierarchy

More questions from this topic