An administrator needs to relocate an existing Google Cloud project from a parent folder named `Staging` to another folder named `Production` within the organization resource hierarchy. The administrator already has the `Project Editor` role directly on the project being relocated, but the migration attempt fails with a permission denied error. Which administrative role or permission requirement explains why this move was denied?
- The administrator requires permissions to detach the project from the source folder and attach it to the destination folder, requiring write permissions on both folders in addition to project update rights.Answer
- BThe Project Editor role grants sufficient authority on the project, but permissions inherited from the child project level automatically override parent folder policies to block folder-to-folder movement.
- CMoving projects between folders cannot be accomplished using predefined roles and strictly requires assigning the primitive Organization Owner role at the root organization node.
- DThe project must first be unlinked from its central Cloud Billing Account because active billing account associations prevent moving projects between resource hierarchy folders.
Answer
The administrator requires write/move permissions on both the source and target parent folders in addition to update permissions on the project itself.
To move a GCP project between folders in the resource hierarchy, an identity must hold rights on all affected nodes: project update permissions on the project being moved, as well as parent modification/move rights (such as `resourcemanager.projects.move` or Project Mover role) on both the source parent folder and the target parent folder.
Step-by-Step Solution
Key Concept
GCP Project Relocation Permission Requirements in Resource Hierarchy
Estimated Time:1m 30s