Examkin

Question

Difficulty: MediumManaging Cloud Projects and Resource Hierarchy

A cloud administrator is establishing governance for a newly acquired business unit in Google Cloud. The administrator needs to set up a dedicated hierarchy branch under the organization node, enforce regional deployment boundaries using organization policy constraints, and place both new and existing workloads into this branch. What is the correct sequence of steps to establish this resource hierarchy and governance structure?

  1. 1Create a new parent Folder named `Retail-Division` directly under the Organization node.
  2. 2Set an Organization Policy constraint (`constraints/gcp.resourceLocations`) on the `Retail-Division` Folder to restrict resource deployment locations.
  3. 3Create a new workload Project `retail-analytics-prod` directly inside the `Retail-Division` Folder.
  4. 4Migrate an existing standalone Project `retail-legacy-app` from the Organization root into the `Retail-Division` Folder.

Answer

The correct sequence is to first create the parent Folder under the Organization node, apply the Organization Policy constraint at the Folder level, create the new workload Project within the Folder, and finally move the existing standalone Project into the Folder.
In Google Cloud resource hierarchy management, structural nodes (Folders) must be created first under the Organization node. Once the container node exists, governance rules such as Organization Policies should be attached at that Folder level so that policy inheritance takes effect. After policy enforcement is established, new projects can be created directly inside the Folder, and existing standalone projects can be migrated into the Folder to inherit the governance constraints.

Step-by-Step Solution

1
Create the parent container (Folder) directly under the Organization node.
Establishes the structural node in the resource hierarchy where policies and child resources will be anchored.
You cannot apply folder-level policies or assign projects to a folder until the folder container itself exists.
2
Apply the Organization Policy constraint to the newly created Folder.
Establishes security and compliance guardrails that automatically propagate down to all child projects via resource hierarchy inheritance.
Setting policies prior to project creation ensures that newly provisioned or migrated workloads immediately comply with corporate governance.
3
Provision the new project inside the configured parent Folder.
The project is initialized directly within the folder governance scope.
Creating the project in the designated folder ensures it inherits the location restrictions defined at the folder level upon creation.
4
Move the existing project into the parent Folder.
The legacy project changes its location in the resource hierarchy and immediately inherits the folder's policy constraints.
Moving an existing project into a folder is performed after policy configuration so that the project instantly aligns with the target folder's active policy state.

Key Concept

Resource hierarchy inheritance and sequential project governance provisioning in Google Cloud.
Rate this question

Topics

Managing Cloud Projects and Resource Hierarchy

More questions from this topic