Courseiva
← ACE
Full test
easyMultiple Choice

Google ACE Practice Question: Refer to the exhibit

Exhibit

Error from gcloud:
$ gcloud projects create my-project --name="My Project"
ERROR: (gcloud.projects.create) Project ID 'my-project' already exists.

Refer to the exhibit. A developer tries to create a new project using the command `gcloud projects create my-project --name="My Project"` and receives the error 'Project ID my-project already exists.' What should the developer do?

⚠ Common exam trap

The trap is confusing project ID with project name; candidates might think the --name flag can be used to avoid the conflict, but the ID must be unique regardless of the name.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use a different project ID

The error indicates that the project ID 'my-project' is already taken globally. Project IDs must be unique across all of Google Cloud. The developer should choose a different project ID that is not in use.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Enable the Cloud Resource Manager API

    Why it's wrong here

    The Cloud Resource Manager API governs project metadata operations; it is already enabled for the create call to return a duplicate-ID error, so enabling it changes nothing. Enabling it is the fix when project creation fails with a service-disabled error, not an ID collision.

  • ✓

    Use a different project ID

    Why this is correct

    Project IDs are globally unique across all of Google Cloud, so `my-project` is already claimed by another organisation and can never be reused. Supplying a different, unused ID satisfies that global uniqueness constraint, while the display name may remain "My Project" since names need not be unique.

  • ✗

    Delete the existing project with the same ID

    Why it's wrong here

    Deleting the existing project destroys its resources and IAM bindings, and project IDs remain reserved after deletion, so the create still fails. Deletion is for decommissioning unwanted projects, not resolving a naming collision; the developer should choose a different globally unique project ID.

  • ✗

    Use the --organization flag

    Why it's wrong here

    The --organization flag only sets the parent resource for the new project; it does not alter the globally unique project ID, so the collision persists. Specifying an organisation is correct when placing projects under a specific org hierarchy, not when the ID is already taken.

About these practice questions

This ACE question is part of Courseiva's 775-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Google Cloud exam blueprint

This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.