Courseiva
Develop for Azure storagehardMultiple ChoiceObjective-mapped

AZ-204 Develop for Azure storage Practice Question

Network Topology
account-name mystorageaccountcontainer-name mycontainerquery "[?properties.contentLength > `1000000`].{name:nameoutput tableRefer to the exhibit.

Refer to the exhibit. You run the Azure CLI command to list blobs in a container that are larger than 1 MB. The command returns no results even though you know there are blobs larger than 1 MB. What is the most likely cause?

⚠ Common exam trap

Microsoft often tests the distinction between Azure Blob Storage and Azure Data Lake Storage Gen2, specifically that the `az storage blob list` command does not work as expected in hierarchical namespace accounts, leading candidates to overlook the storage account type as the root cause.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The storage account has hierarchical namespace enabled (Azure Data Lake Storage Gen2)

The Azure CLI command uses the `az storage blob list` command with a JMESPath query to filter blobs larger than 1 MB. However, when a storage account has hierarchical namespace enabled (Azure Data Lake Storage Gen2), the blob listing API returns directory entries and file entries in a flat list, but the `az storage blob list` command does not support the hierarchical namespace by default. The command may return no results because the underlying REST API (Blob Service REST API) does not properly enumerate blobs in a Data Lake Storage Gen2 account without using the `--use-hierarchical-namespace` flag or the `az storage fs file list` command instead. This is a known limitation where the standard blob list operation fails to list files in a hierarchical namespace-enabled account.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The JMESPath query uses backticks incorrectly

    Why it's wrong here

    The JMESPath query `properties.creationTime` correctly uses backticks to delimit the literal string 'creationTime' if it were a non-identifier key, but in this case, `creationTime` is a valid identifier. The backticks are syntactically valid and do not cause the query to fail; rather, the issue lies with the structure of the input JSON not matching the queried path, causing an empty result.

  • The storage account has hierarchical namespace enabled (Azure Data Lake Storage Gen2)

    Why this is correct

    When a storage account has hierarchical namespace enabled, effectively becoming Azure Data Lake Storage Gen2, the JSON output schema for `az storage blob list` changes significantly. Unlike standard Blob Storage, the `properties` object, or specifically `properties.creationTime`, may not exist or be structured differently within the returned JSON for each item. Consequently, the JMESPath query `properties.creationTime` will fail to find a match in the altered schema, resulting in an empty list even if blobs are present.

  • The --container-name parameter is case-sensitive

    Why it's wrong here

    While Azure Storage container names are indeed case-sensitive and must adhere to specific naming conventions, including being entirely lowercase, an incorrect or non-existent container name would typically lead to a direct error from the `az storage blob list` command. The command would fail with a 'ContainerNotFound' or similar error, rather than successfully executing and returning an empty list of blobs, indicating the container name provided was likely valid.

  • The --account-name parameter is incorrect

    Why it's wrong here

    An incorrect `--account-name` parameter would prevent the Azure CLI from successfully authenticating or locating the specified storage account entirely. If the account name were invalid or misspelled, the `az storage blob list` command would terminate with a clear error message indicating that the storage account could not be found or accessed. It would not execute successfully and simply return an empty list of blobs, which implies the account name was correctly identified.

About these practice questions

This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.