Output formatting in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Cloud Storage Bucket Output Formatting

You create a Google Cloud Storage bucket with uniform bucket-level access enabled. When you list the bucket's IAM policies using gcloud CLI, what is the format of the output?

A An XML document listing roles and members.

B A YAML formatted list showing roles and members with indentation.

C A plain text list of roles without member details.

D A JSON object showing the roles and members with no nested fields.

💡 Hint

gcloud CLI often outputs YAML by default for policy listings.

The gcloud storage buckets get-iam-policy command outputs the IAM policy in YAML format by default. This includes roles and their associated members with indentation to show hierarchy.

❓ Configuration

intermediate

Formatting Output of gcloud Compute Instances List

You run the command gcloud compute instances list. How can you format the output to show only instance names and their zones in a table format?

A gcloud compute instances list --format="table(name, zone)"

B gcloud compute instances list --format="json(name, zone)"

C gcloud compute instances list --format="csv(name, zone)"

D gcloud compute instances list --format="text(name, zone)"

💡 Hint

Table format shows columns with headers.

The --format="table(name, zone)" option formats the output as a table with columns for name and zone.

❓ Architecture

advanced

Choosing Output Format for Cloud Logging Export

You configure a Cloud Logging export sink to BigQuery. Which output format will BigQuery receive from the logs export?

A Plain text log entries without structure.

B CSV format with comma-separated values.

C XML formatted logs with tags.

D Structured JSON format with nested fields preserved.

💡 Hint

BigQuery works best with structured data.

Cloud Logging exports logs to BigQuery in structured JSON format preserving nested fields for querying.

❓ security

advanced

Output Formatting Impact on Secret Manager Access Logs

When viewing Secret Manager access logs in Cloud Logging, what output format helps security analysts quickly identify unauthorized access attempts?

A JSON format with fields like principalEmail and methodName clearly labeled.

B Plain text logs with all details in one line.

C CSV format listing only timestamps and resource names.

D XML format with nested tags for each log entry.

💡 Hint

Structured logs help filter and search specific fields.

JSON formatted logs with labeled fields allow easy filtering and searching for security events.

✅ Best Practice

expert

Best Output Format for Automated Cloud Monitoring Alerts

You want to configure Cloud Monitoring alert policies to send notifications with output that is easy to parse by automation tools. Which output format should you choose for the alert message payload?

A HTML formatted email with styling.

B Plain text summary of the alert.

C JSON format with structured fields for alert details.

D CSV format listing alert metrics.

💡 Hint

Automation tools parse structured data more easily.

JSON format provides structured data that automation tools can parse and act on reliably.

Practice

1. What does the --format flag do in Google Cloud CLI commands?

easy

A. It installs additional plugins for the CLI.

B. It changes how the command output is displayed.

C. It updates the project ID automatically.

D. It sets the region for the command execution.

Solution

1. Step 1: Understand the purpose of --format

   The --format flag controls the display style of the command output in Google Cloud CLI.

2. Step 2: Compare with other options

   Options A, B, and C relate to configuration or installation, not output formatting.

3. Final Answer:

   It changes how the command output is displayed. -> Option B

4. Quick Check:

   Output formatting = changes display style [OK]

Hint: Remember: --format controls output style, not settings [OK]

Common Mistakes:

• Confusing --format with region or project settings
• Thinking it installs plugins
• Assuming it changes command behavior

2. Which of the following is the correct syntax to get a JSON output from a gcloud command?

easy

A. gcloud compute instances list -format=json

B. gcloud compute instances list --output=json

C. gcloud compute instances list --format=json

D. gcloud compute instances list --format=table

Solution

1. Step 1: Identify the correct flag for output format

   The correct flag is --format, not --output or -format.

2. Step 2: Check the format value

   JSON format is specified as json, so --format=json is correct. gcloud compute instances list --format=table uses table format, which is not JSON.

3. Final Answer:

   gcloud compute instances list --format=json -> Option C

4. Quick Check:

   Use --format=json for JSON output [OK]

Hint: Use --format=json exactly for JSON output [OK]

Common Mistakes:

• Using --output instead of --format
• Using single dash -format
• Choosing wrong format like table for JSON output

3. What will be the output format of this command?
gcloud projects list --format='table(projectId, name)'

medium

A. A plain text list of project IDs only

B. A JSON array with projectId and name fields

C. A YAML list of projects with projectId and name

D. A table showing columns projectId and name

Solution

1. Step 1: Analyze the format flag value

   The format is set to table(projectId, name), which means output will be a table with those two columns.

2. Step 2: Understand output types

   JSON or YAML would require json or yaml formats, not table. Plain text list is not specified.

3. Final Answer:

   A table showing columns projectId and name -> Option D

4. Quick Check:

   table(...) format = table output [OK]

Hint: Table format shows columns named inside parentheses [OK]

Common Mistakes:

• Confusing table format with JSON or YAML
• Expecting plain text output
• Ignoring parentheses in format

4. You run gcloud compute instances list --format=json but get an error. What is the most likely cause?

medium

A. Your gcloud CLI version is outdated and does not support JSON format.

B. You forgot to authenticate with gcloud auth login.

C. You typed --format=json incorrectly with a space.

D. The project has no compute instances, so JSON output is empty.

Solution

1. Step 1: Check common syntax errors

   The syntax --format=json is correct; spaces inside the flag are not allowed but usually cause different errors.

2. Step 2: Consider CLI version compatibility

   Older gcloud versions may not support JSON output format, causing errors.

3. Step 3: Authentication and empty output

   Authentication errors cause different messages; empty output does not cause errors.

4. Final Answer:

   Your gcloud CLI version is outdated and does not support JSON format. -> Option A

5. Quick Check:

   Old CLI versions may lack JSON support [OK]

Hint: Update gcloud CLI if JSON format causes errors [OK]

Common Mistakes:

• Assuming syntax error when syntax is correct
• Blaming authentication for format errors
• Thinking empty output causes errors

5. You want to share a list of VM instances with your team in a readable format that includes instance name and zone. Which command and format should you use?

hard

A. gcloud compute instances list --format='table(name, zone)'

B. gcloud compute instances list --format='json(name, zone)'

C. gcloud compute instances list --format='yaml(name, zone)'

D. gcloud compute instances list --format='text(name, zone)'

Solution

1. Step 1: Identify readable formats for sharing

   Table format is easy to read and share with columns clearly shown.

2. Step 2: Check format syntax and readability

   JSON, YAML, and text support field projections but produce less human-readable output compared to table's columnar display.

3. Step 3: Confirm correct command

   --format='table(name, zone)' correctly formats output as a table with those columns.

4. Final Answer:

   gcloud compute instances list --format='table(name, zone)' -> Option A

5. Quick Check:

   Use table(...) for readable column output [OK]

Hint: Use table format with columns for readable shared output [OK]

Common Mistakes:

• Using JSON or YAML with column lists (less readable)
• Choosing text format which lacks columns
• Not specifying columns inside table format