An enterprise organization is restructuring its Google Cloud environment to establish proper governance and centralized resource management. A cloud engineer is tasked with migrating a standalone GCP project into a newly established 'Finance-Prod' folder beneath the Organization node, linking it to the organization's central billing account, and enforcing resource configuration constraints. Arrange the administrative steps in the correct chronological order to complete this deployment while following Google recommended best practices.
- 1Create the target 'Finance-Prod' folder under the Organization resource node using the Resource Manager CLI.
- 2Move the existing standalone project into the newly created 'Finance-Prod' folder container.
- 3Link the project to the centralized Organization Billing Account.
- 4Apply an Organization Policy constraint at the 'Finance-Prod' folder node to restrict public IP assignments.
- 5Verify effective Organization Policy inheritance and compliance at the project level.
Answer
The correct sequence starts with provisioning the destination folder under the Organization root, moving the standalone project into that folder, linking the project to the designated billing account, enforcing the required Organization Policy constraint at the folder level, and finally verifying that the project correctly inherits the effective policy constraints.
The correct operational order follows the logical dependency tree of Google Cloud resource hierarchy creation: first establish the parent container (folder under organization), second move the child resource (project into folder), third establish financial linkage (link billing account), fourth apply policy constraints at the container node (folder organization policy), and fifth audit effective inherited governance at the leaf level (project policy evaluation).
Step-by-Step Solution
Key Concept
GCP Resource Hierarchy Lifecycle & Policy Inheritance Sequence