Question

Difficulty: MediumManaging Cloud Projects and Resource Hierarchy

An organization is decommissioning a legacy application hosted in Google Cloud. An Associate Cloud Engineer attempts to shut down the project using the gcloud command-line tool, but the command fails with an error indicating that the project cannot be deleted because a lien exists on the resource. Which action should the engineer take to resolve this issue and successfully shut down the project?

  1. Identify and delete the active lien placed on the project before re-executing the project deletion command.Answer
  2. B
    Remove inherited IAM policies at the parent Folder level so that project deletion protection constraints are ignored.
  3. C
    Grant the primitive Owner role on the linked Cloud Billing Account to force the deletion operation.
  4. D
    Submit a GCP quota increase request to expand the organization's maximum project deletion limit.

Answer

Identify and delete the active lien placed on the project before re-executing the project deletion command.
In Google Cloud, project liens prevent accidental project deletion. When a lien is active on a project, any attempt to shut down or delete the project fails until an authorized user removes the lien object.

Step-by-Step Solution

1
Inspect active liens on the project.
List the project liens using `gcloud alpha liens list` or the Resource Manager API.
Liens block project deletion requests to prevent accidental destruction of critical resources.
2
Delete the specific lien object.
Execute `gcloud alpha liens delete [LIEN_ID]` to remove the lifecycle lock.
A project cannot enter the 30-day shutdown phase while an active lien is attached.
3
Re-run the project shutdown command.
Execute `gcloud projects delete [PROJECT_ID]` successfully.
Once all liens are removed, standard project deletion permissions apply.

Key Concept

Project Lifecycle Management and Project Liens
Estimated Time:1m 30s
Rate this question