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.

• ✗

  Open separate terminal windows for each project.

  Why it's wrong here

  Opening separate terminal windows per project does not inherently switch GCP contexts; each window still uses the same default active gcloud configuration unless you manually export environment variables such as CLOUDSDK_ACTIVE_CONFIG_NAME or run gcloud config configurations activate in each one. This creates fragile, memory-based management that fails when you forget which window maps to which project, and it doesn't scale to automating project switches in scripts or CI/CD pipelines. It is a workaround, not a CLI-based solution.

• ✗

  Run gcloud init every time you switch projects.

  Why it's wrong here

  gcloud init is an interactive setup command that walks through authentication, selects a default project, and configures account preferences from scratch. Running it each time you switch projects is overkill because it re-initializes the entire configuration, possibly forcing re-authentication and resetting custom properties you had previously set. It also prompts for input and overwrites the currently active configuration, making frequent switching slow, disruptive, and prone to accidentally erasing environment-specific settings.

• ✗

  Use gcloud config set project each time you switch.

  Why it's wrong here

  Using gcloud config set project only changes the project property inside the single active configuration, leaving other settings like compute/region, account, or custom quotas untouched. This means if you switch between projects that require different regions or service accounts, you must issue multiple gcloud config set commands individually for each property, which is tedious and error-prone. Additionally, this mutates one shared configuration, so every switch requires manual resetting, whereas configurations isolate these values cleanly for instant, reversible switching.

• ✓

  Create multiple configuration profiles and activate them as needed.

  Why this is correct

  Creating multiple named configurations with gcloud config configurations create and activating them via gcloud config configurations activate is the officially recommended pattern for frequent context switching. Each configuration stores its own project, account, region, and other properties, so you can define a distinct environment for every GCP project or workflow. Activation is instantaneous and deterministic, and you can even use the --configuration flag to run a single command in a non-default configuration without changing your active context, enabling safe automation and parallel work.

Go deeper

Related to this question