A cloud architect is developing an administrative shell script to automate operational maintenance across multiple environments that use distinct service accounts and settings. The script must satisfy the following technical requirements: Seamlessly switch execution context between predefined environments without prompting for user authentication during execution. Override specific properties on individual commands without permanently modifying the stored environment properties. Extract specific resource property values directly into shell variables without table borders, column headers, or extraneous metadata. Which combination of gcloud CLI commands and flags meets these requirements?

Switch contexts using `gcloud config configurations activate`, apply per-invocation overrides using command flags such as `--project`, and extract raw attribute values using `--format="value(PROPERTY)"`.: ### What Named Configurations and Format Flags Are In the Google Cloud CLI, a **named configuration** is a distinct, saved group of settings and properties (such as authenticated accounts, target projects, default regions, and zones). The `gcloud config configurations activate` command switches the active CLI profile to the specified configuration instantly. To format output for administrative scripting, the global `--format` flag controls the output projection, where the `value()` transform prints raw property values without headers or decoration. ### How It Meets All Requirements - **Seamless Context Switching**: Running `gcloud config configurations activate ` switches all active CLI properties—including authentication identity and default project—without interactive prompts or credential re-entry. - **Per-Invocation Overrides**: Utilizing command flags like `--project PROJECT_ID` takes precedence over stored configuration properties for only that specific execution, leaving the active configuration's underlying properties unchanged. - **Clean Script Parsing**: The `--format="value(PROPERTY)"` expression strips all table headers, borders, and wrapper formatting, printing only the requested property value so it can be assigned directly to shell variables. ### Key Advantages and Capabilities - **Isolated Profiles**: Allows maintaining independent environments (e.g., development, staging, production) with unique default zones, regions, and accounts. - **Non-Destructive Overrides**: Command-line flags always override persistent properties on a per-command basis without mutating configuration files. - **Native Script Integration**: Combining `value()` formatting with shell variable assignments eliminates the need for complex external text processing tools like `awk`, `sed`, or `cut`. - **Unattended Execution**: Automations can switch between multiple Google Cloud tenants and project hierarchies programmatically. ### Why This Is Optimal This pattern leverages native Google Cloud SDK configuration management features. It completely avoids error-prone shell text parsing, maintains isolated credential contexts, and avoids persistent state corruption caused by repeatedly mutating active configuration properties.

StudyCerts

Gcloud Cli Configuration Switching Formatting Flags | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Gcloud Cli Configuration Switching Formatting Flags

Section: Google Cloud SDKs (e.g., gcloud, gsutil, and bq)

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A cloud architect is developing an administrative shell script to automate operational maintenance across multiple environments that use distinct service accounts and settings.

The script must satisfy the following technical requirements:

Seamlessly switch execution context between predefined environments without prompting for user authentication during execution.
Override specific properties on individual commands without permanently modifying the stored environment properties.
Extract specific resource property values directly into shell variables without table borders, column headers, or extraneous metadata.

Which combination of gcloud CLI commands and flags meets these requirements?

Switch contexts by setting gcloud config set core/project, apply per-invocation overrides using gcloud config configurations describe, and extract raw attribute values using --format="text".

Switch contexts using gcloud config configurations activate, apply per-invocation overrides using command flags such as --project, and extract raw attribute values using --format="value(PROPERTY)".

Switch contexts using gcloud init --skip-diagnostics, set per-invocation overrides using gcloud config set, and extract raw attribute values using --format="table[no-heading](PROPERTY)".

Switch contexts by deleting and recreating profiles using gcloud config configurations delete and create, apply per-invocation overrides using gcloud config unset, and extract raw attribute values using --format="flattened(PROPERTY)".

Professional Cloud Architect

Gcloud Cli Configuration Switching Formatting Flags

Related questions