The correct answer is that the logs are written to resource-specific tables instead of AzureDiagnostics. When you change a diagnostic setting for a storage account from the legacy AzureDiagnostics mode to Resource-specific mode, the log data is no longer routed to the consolidated AzureDiagnostics table; instead, it is directed to dedicated tables such as StorageReadLogs or StorageWriteLogs. This is why a query targeting AzureDiagnostics returns no rows—the logs are now stored in the new, separate table format. On the AZ-104 exam, this concept tests your understanding of Azure Monitor diagnostic settings and the two log destination modes, often appearing as a trick where candidates assume all logs always land in AzureDiagnostics. A common trap is forgetting that changing the mode changes the table destination, not just the log collection. Memory tip: “Resource-specific means table-specific—if you change the mode, change your query.”
AZ-104 Monitor and Maintain Azure Resources Practice Question
This AZ-104 practice question tests your understanding of monitor and maintain azure resources. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
Exhibit
Storage account diagnostic settings
- Destination: Log Analytics workspace
- Categories: allLogs
- Export mode: Resource-specific
Troubleshooting note:
- A coworker ran: AzureDiagnostics | where ResourceProvider == "MICROSOFT.STORAGE"
- Result: No matching records
Based on the exhibit, why does a query against AzureDiagnostics return no rows after the storage account diagnostic setting was changed?
Storage account diagnostic settings
- Destination: Log Analytics workspace
- Categories: allLogs
- Export mode: Resource-specific
Troubleshooting note:
- A coworker ran: AzureDiagnostics | where ResourceProvider == "MICROSOFT.STORAGE"
- Result: No matching records
A
The storage account cannot send logs to Log Analytics when public network access is disabled.
Why wrong: Network access does not determine the log table format used in Log Analytics.
B
The logs are written to resource-specific tables instead of AzureDiagnostics.
When diagnostic settings use resource-specific mode, Azure writes records to service-specific tables rather than the legacy AzureDiagnostics table. The query failed because it looked in the wrong table. The administrator should query the table that matches the storage log source or switch the destination format if a unified table is preferred.
C
The diagnostic setting only sends metrics, not logs, to the workspace.
Why wrong: The exhibit shows allLogs were selected, so logs are being collected rather than metrics only.
D
The workspace retention period automatically deletes all records after one hour.
Why wrong: Workspace retention does not explain why the query returned no rows immediately after logging was enabled.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The logs are written to resource-specific tables instead of AzureDiagnostics.
Option B is correct because when you change a diagnostic setting for a storage account from 'AzureDiagnostics' mode to 'Resource-specific' mode, logs are no longer sent to the AzureDiagnostics table. Instead, they are written to dedicated resource-specific tables (e.g., StorageReadLogs, StorageWriteLogs). Since the query targets AzureDiagnostics, it returns no rows because the logs are now stored in the new table format.
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 storage account cannot send logs to Log Analytics when public network access is disabled.
Why it's wrong here
Network access does not determine the log table format used in Log Analytics.
✓
The logs are written to resource-specific tables instead of AzureDiagnostics.
Why this is correct
When diagnostic settings use resource-specific mode, Azure writes records to service-specific tables rather than the legacy AzureDiagnostics table. The query failed because it looked in the wrong table. The administrator should query the table that matches the storage log source or switch the destination format if a unified table is preferred.
Related concept
Read the scenario before looking for a memorised answer.
✗
The diagnostic setting only sends metrics, not logs, to the workspace.
Why it's wrong here
The exhibit shows allLogs were selected, so logs are being collected rather than metrics only.
✗
The workspace retention period automatically deletes all records after one hour.
Why it's wrong here
Workspace retention does not explain why the query returned no rows immediately after logging was enabled.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume logs are always written to the AzureDiagnostics table, overlooking that the diagnostic setting can be configured to use resource-specific tables, which changes the destination table name and causes queries against AzureDiagnostics to return no rows.
Trap categories for this question
Command / output trap
The exhibit shows allLogs were selected, so logs are being collected rather than metrics only.
Detailed technical explanation
How to think about this question
Under the hood, Azure Monitor diagnostic settings support two destination table modes: 'Azure Diagnostics' (legacy) which aggregates all resource logs into a single AzureDiagnostics table, and 'Resource-specific' which creates separate tables per log category (e.g., StorageReadLogs, StorageWriteLogs). When you switch modes, existing data in AzureDiagnostics remains, but new logs flow only to the resource-specific tables. This is critical for storage accounts because the schema is more granular and query performance improves with smaller, targeted tables. In real-world scenarios, if you migrate to resource-specific mode without updating your KQL queries, you will see zero results in AzureDiagnostics, leading to false assumptions of data loss.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Monitor and Maintain Azure Resources — This question tests Monitor and Maintain Azure Resources — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The logs are written to resource-specific tables instead of AzureDiagnostics. — Option B is correct because when you change a diagnostic setting for a storage account from 'AzureDiagnostics' mode to 'Resource-specific' mode, logs are no longer sent to the AzureDiagnostics table. Instead, they are written to dedicated resource-specific tables (e.g., StorageReadLogs, StorageWriteLogs). Since the query targets AzureDiagnostics, it returns no rows because the logs are now stored in the new table format.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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-104 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-104 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.