GCP Associate Cloud Engineer Practice Question 62: Moving Project Between Folders
Google Cloud Associate Cloud Engineer · Test 7 · question 2 of 10
An administrator runs gcloud projects move to relocate the project finance-app from the sandbox folder to the prod-finance folder in the same organization. A custom IAM role is bound directly on finance-app, granting a service account access to Cloud SQL. The sandbox folder has no resource location restriction, while prod-finance has an organization policy that restricts new resources to us locations.
What should the administrator expect, and what access does moving the project require?
Show answer and explanation
Answer:
IAM policies and organization policies bound directly to a project travel with it, so the custom role granting Cloud SQL access to the service account is untouched by the move. Inheritance, however, is evaluated from the project's current position in the hierarchy: once finance-app is under prod-finance, it stops inheriting anything from sandbox and instead inherits prod-finance's bindings and organization policies, including the us-only location restriction. Performing the move itself needs the resourcemanager.projects.move permission on both the source folder and the destination folder (bundled in the predefined Project Mover role), plus resourcemanager.projects.update on the project; access on only one folder is not enough.
Option A is wrong because direct project-level bindings are not reset by a move, and Owner on the project alone does not grant the folder-level permission needed to relocate it. Option C is wrong because moving a project with existing resources is a supported, routine operation and does not require deleting anything. Option D is wrong because inherited policy comes from the current parent in the hierarchy, so sandbox's policy stops applying the moment the project moves under prod-finance.
Reference: Move a project