The answer is that the Azure CLI `az keyvault secret show` command returns only metadata by default, and you must specify `--query "value"` to retrieve the actual secret value. This behavior occurs because the command is designed to output the full secret object, which includes attributes like `id`, `enabled`, and `updated`, but the sensitive `value` property is excluded from the default response for security and performance reasons. On the Microsoft Azure Developer Associate AZ-204 exam, this tests your understanding of Azure CLI query syntax and Key Vault secret retrieval patterns—a common trap is assuming the value appears automatically, leading to confusion when only metadata is shown. To remember this, think of the CLI as a vault door: `show` opens the door to see the label (metadata), but you need `--query "value"` to actually take the secret out.
AZ-204 Implement Azure security Practice Question
This AZ-204 practice question tests your understanding of implement azure security. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Network Topology
Refer to the exhibit. You run the Azure CLI command to retrieve a secret from Azure Key Vault. The output shows the secret metadata but not the secret value. The command returns without error. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The command output only shows metadata by default; you must specify --query "value" to retrieve the secret value.
The Azure CLI `az keyvault secret show` command returns the secret metadata (including attributes like id, enabled, created, updated) by default, but does not include the secret value unless you explicitly request it using the `--query "value"` parameter. Since the command completed without error and only metadata was shown, the most likely cause is that the output was not filtered to retrieve the secret value.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 secret has expired.
Why it's wrong here
The expires field is null, indicating no expiration.
✗
The user does not have the Key Vault Secrets Officer role.
Why it's wrong here
The command returned metadata, so the user has read access.
✗
The secret is in a soft-deleted state.
Why it's wrong here
Soft-deleted secrets cannot be retrieved without recovery.
✓
The command output only shows metadata by default; you must specify --query "value" to retrieve the secret value.
Why this is correct
The Azure CLI hides secret values by default.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume the command output includes the secret value by default, but Azure CLI intentionally omits it for security, requiring an explicit `--query "value"` to retrieve the actual secret.
Trap categories for this question
Command / output trap
The command returned metadata, so the user has read access.
Detailed technical explanation
How to think about this question
The Azure CLI uses Azure REST API calls under the hood; the `az keyvault secret show` command sends a GET request to `{vaultBaseUrl}/secrets/{secret-name}/{secret-version}?api-version=7.4`. The response includes both the `value` field and the `attributes` object, but the CLI's default output format (table, json, or yaml) only displays the top-level metadata fields unless you use `--query` to project the `value` property. This is a common design pattern in Azure CLI to avoid accidentally exposing sensitive data in logs or terminal history.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Implement Azure security — This question tests Implement Azure security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The command output only shows metadata by default; you must specify --query "value" to retrieve the secret value. — The Azure CLI `az keyvault secret show` command returns the secret metadata (including attributes like id, enabled, created, updated) by default, but does not include the secret value unless you explicitly request it using the `--query "value"` parameter. Since the command completed without error and only metadata was shown, the most likely cause is that the output was not filtered to retrieve the secret value.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.