Output formats (json, table, tsv) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Azure CLI output format behavior

When you run the Azure CLI command az vm list --output json, what is the format of the output you receive?

A A plain text table with columns for VM properties.

B A tab-separated values (TSV) list with VM names only.

C An XML document describing the virtual machines.

D A JSON array containing objects representing each virtual machine.

💡 Hint

Think about what the 'json' output format means in Azure CLI.

The 'json' output format returns data as a JSON array with detailed objects for each VM, suitable for programmatic use.

❓ service_behavior

intermediate

Azure CLI table output format characteristics

What does the Azure CLI command az vm list --output table display?

A A CSV file download of VM data.

B A JSON array with detailed VM information.

C A formatted table with columns and rows showing VM properties in a readable way.

D A list of VM names separated by commas.

💡 Hint

The 'table' output is designed for easy reading in the terminal.

The 'table' format shows a human-friendly table with columns and rows summarizing VM info.

❓ service_behavior

advanced

Azure CLI TSV output format usage

If you run az vm list --output tsv, what is the expected output format?

A A tab-separated list of VM properties with headers, suitable for scripting.

B A formatted table with headers and borders.

C A JSON object with nested VM details.

D An HTML table showing VM information.

💡 Hint

TSV means values separated by tabs, often used in scripts.

The 'tsv' output is a plain text format with values separated by tabs, including headers, ideal for scripts.

🧠 Conceptual

advanced

Choosing output format for automation scripts

You want to automate processing Azure VM data in a script that parses output easily. Which Azure CLI output format is best?

A None, because Azure CLI does not support output formats.

B JSON, because it provides structured data easy to parse programmatically.

C TSV, because it includes headers and formatting.

D Table, because it is easy to read for humans.

💡 Hint

Think about which format scripts can parse without extra work.

JSON is structured and widely supported for parsing in scripts, unlike table or TSV which may require extra parsing logic.

❓ security

expert

Security implications of output formats in Azure CLI

Which output format should you avoid when displaying sensitive Azure resource information in a shared terminal session to reduce risk of accidental exposure?

A JSON, because it shows full structured details including secrets or keys if present.

B Table, because it shows summarized info that might omit sensitive details.

C TSV, because it hides sensitive data by default.

D None, all output formats automatically mask sensitive data.

💡 Hint

Consider which format reveals the most raw data.

JSON output often includes all data fields, including sensitive ones, so it should be handled carefully in shared environments.

Practice

1. What is the main reason to use --output json when running Azure CLI commands?

easy

A. To shorten the output for quick reading

B. To display results in a colorful table format

C. To export data as a tab-separated file

D. To get output that machines and scripts can easily read

Solution

1. Step 1: Understand output formats purpose

   JSON format is structured and easy for programs to parse and use.

2. Step 2: Compare with other formats

   Table and TSV are better for humans to read or export, not for machines.

3. Final Answer:

   To get output that machines and scripts can easily read -> Option D

4. Quick Check:

   JSON = machine-friendly output [OK]

Hint: JSON output is for scripts; table/TSV is for people [OK]

Common Mistakes:

• Confusing JSON with table format
• Thinking TSV is for machine parsing only
• Assuming JSON output is shorter

2. Which Azure CLI command correctly sets the output format to table?

easy

A. az vm list --output table

B. az vm list --format table

C. az vm list -o json

D. az vm list --output tsv

Solution

1. Step 1: Identify correct syntax for output option

   The correct flag to set output format is --output or -o.

2. Step 2: Match the format value

   To get table format, use --output table. Other options are either wrong flag or different formats.

3. Final Answer:

   az vm list --output table -> Option A

4. Quick Check:

   Use --output table for table format [OK]

Hint: Use --output or -o followed by format name [OK]

Common Mistakes:

• Using --format instead of --output
• Mixing output format names
• Using -o json when table is needed

3. What will be the output format of this command?
az storage account list -o tsv

medium

A. Tab-separated values without headers

B. A human-friendly table with headers

C. A JSON array of storage accounts

D. An error because tsv is invalid

Solution

1. Step 1: Understand the -o tsv flag

   The tsv output format produces tab-separated values, useful for scripts or exporting.

2. Step 2: Check if headers are included

   TSV output usually does not include headers, just raw data separated by tabs.

3. Final Answer:

   Tab-separated values without headers -> Option A

4. Quick Check:

   TSV = tab-separated, no headers [OK]

Hint: TSV outputs raw tab-separated data, no headers [OK]

Common Mistakes:

• Thinking TSV includes headers like table
• Confusing TSV with JSON format
• Assuming TSV causes errors

4. You run az group list --output tsv but get an error. What is the most likely cause?

medium

A. You forgot to install Azure CLI

B. The Azure subscription is not set

C. You used the wrong flag; it should be --output table

D. The command does not support TSV output format

Solution

1. Step 1: Check common prerequisites

   az group list requires an active Azure subscription (via az login and az account set-subscription).

2. Step 2: Eliminate other causes

   TSV is fully supported, CLI issues prevent az from running at all, wrong flag like table would output table instead of error.

3. Final Answer:

   The Azure subscription is not set -> Option B

4. Quick Check:

   No subscription -> auth error on list [OK]

Hint: Run az login & az account set-subscription first [OK]

Common Mistakes:

• Assuming TSV unsupported (all standard formats work)
• CLI install confusion (command runs but auth fails)
• Wrong flag mixup (tsv is valid)

5. You want to export a list of Azure VMs with their names and locations in a format easy to import into Excel. Which command and output format should you use?

hard

A. az vm list --query '[].{Name:name, Location:location}' -o table

B. az vm list --query '[].{Name:name, Location:location}' -o json

C. az vm list --query '[].{Name:name, Location:location}' -o tsv

D. az vm list --output yaml

Solution

1. Step 1: Choose output format for Excel import

   TSV (tab-separated values) is easy to import into Excel as columns.

2. Step 2: Use query to select needed fields

   The query selects only VM name and location, simplifying the output.

3. Final Answer:

   az vm list --query '[].{Name:name, Location:location}' -o tsv -> Option C

4. Quick Check:

   TSV + query = Excel-friendly export [OK]

Hint: Use -o tsv with query for Excel import [OK]

Common Mistakes:

• Using JSON which Excel needs extra steps to import
• Using table which is for human reading only
• Using unsupported YAML format