Google ACE Setting Up a Cloud Solution Environment Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  gcloud config set project my-new-project

  Why it's wrong here

  This command only sets the currently active project in the local gcloud configuration (typically in the ~/.config/gcloud/configuration directory). It does not interact with the Cloud Resource Manager API to create a new project. The project must already exist in the GCP organization or as a standalone project; otherwise subsequent commands that require the project will fail with a 404 or permission error. Therefore, it is an operation to switch the default project context, not a creation command.

• ✓

  gcloud projects create my-new-project

  Why this is correct

  This is the canonical command for creating a new Google Cloud project via the CLI. It calls the Cloud Resource Manager projects.create API method, and requires the resourcemanager.projects.create permission (provided by the Project Creator IAM role). The command returns a project ID and number, and initially places the project in the 'ACTIVE' lifecycle state unless an organization policy restricts it. Use `--organization` or `--folder` flags to specify the parent resource.

• ✗

  gcloud alpha projects create my-new-project

  Why it's wrong here

  While `gcloud alpha` provides access to experimental commands, this particular project creation functionality is not experimental; it is stable and available in the core `gcloud` CLI. Using the `alpha` prefix is unnecessary and could lead to using a version of the command that may have different flags or behavior, potentially causing compatibility issues. Since `gcloud projects create` exists as a GA (generally available) command, the alpha variant does not provide any additional benefit for standard project creation.

• ✗

  gcloud init my-new-project

  Why it's wrong here

  `gcloud init` performs an SDK initialization workflow: it sets up the local configuration, authenticates the user, and then optionally creates a new project *if* it doesn't exist. However, this command is interactive and driven by a wizard, not a direct project creation command. Passing an argument like `my-new-project` to `gcloud init` sets the project ID that the wizard will use, but the command's primary purpose is to initialize the SDK environment, and it will only create the project after user confirmation during the interactive flow. For non-interactive automation, the explicit `gcloud projects create` is the appropriate choice.

Go deeper

Related to this question