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.

• ✗

  Run 'gcloud init' and select 'Create a new configuration'

  Why it's wrong here

  gcloud init is an interactive wizard that sets up default configuration and can create new configurations, but it doesn't support specifying a configuration name as a command-line argument; you would still need to explicitly create and name the configuration using gcloud config configurations create. Furthermore, running gcloud init might reset or alter your current configuration if you're not careful, making it unsuitable for managing multiple named configurations in a scripted or reproducible way.

• ✓

  Run 'gcloud config configurations create prod' then 'gcloud config set project prod-project'

  Why this is correct

  The correct method is to first run gcloud config configurations create prod, which generates a new empty named configuration and automatically activates it. With the prod configuration active, gcloud config set project prod-project then sets the project property for that configuration, providing a clean, isolated environment for managing the prod project.

• ✗

  Run 'gcloud config set project prod-project' with a flag to create new config

  Why it's wrong here

  There is no flag on gcloud config set project that creates a new configuration; this command only updates properties in the currently active configuration. Passing an imaginary flag like --new-configuration would be rejected because the gcloud CLI does not define such a flag. To create a new configuration, you must explicitly use the gcloud config configurations create subcommand; no single gcloud config set invocation can create a configuration.

• ✗

  Edit the gcloud config file manually

  Why it's wrong here

  Manually editing the gcloud configuration files is error-prone because these files are structured and managed by the CLI, and an improper edit can corrupt the configuration or cause surprising behavior in your shell. The gcloud CLI also does not guarantee backward compatibility for the file formats across versions, so hand-editing is fragile. Instead, use the gcloud config set and gcloud config configurations commands to safely modify properties and create configurations.

Go deeper

Related to this question