AZ-104 Monitor and Maintain Azure Resources Practice Question
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?
⚠ Common exam trap
It's easy for candidates to 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.
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 logs are written to resource-specific tables instead of AzureDiagnostics.
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.
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
Public network access on a storage account only controls direct access to that storage endpoint; diagnostic logs are transmitted over the Azure internal backend to Log Analytics, so even with public access disabled, logs still flow normally. Network configuration does not influence the table format used for log storage in Log Analytics. Therefore, the query returns nothing because the logs reside in a resource-specific table, not because of any network access restrictions.
When this WOULD be correct
This would be correct if the question described a scenario where a storage account has public network access disabled (e.g., using a private endpoint) and the diagnostic setting is configured to send logs to a Log Analytics workspace. In that case, network isolation would prevent log delivery, resulting in no rows in AzureDiagnostics.
- ✓
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.
- ✗
The diagnostic setting only sends metrics, not logs, to the workspace.
Why it's wrong here
The diagnostic setting exhibit explicitly selects the 'allLogs' category, which forwards all available log categories to the destination, not just metrics. Metrics are collected separately and would be written to the AzureMetrics table, not to AzureDiagnostics, so the query's failure to find data is unrelated to a metrics-only configuration. Since the query targets AzureDiagnostics and receives no rows, the actual problem is that logs are stored in a resource-specific table.
When this WOULD be correct
This option would be correct if the diagnostic setting was configured to send only metrics (e.g., 'AllMetrics') to the Log Analytics workspace, and the query was for log data. For example, a question where the setting exports only performance counters and no log categories.
- ✗
The workspace retention period automatically deletes all records after one hour.
Why it's wrong here
Workspace retention controls how long logs are retained after ingestion, not an immediate one-hour purge. Even if the retention period were set to its minimum, Log Analytics does not delete records instantly upon arrival, and a query would return an empty result set rather than a table-not-found error. The real cause is that the diagnostic setting writes to resource-specific tables, so the legacy AzureDiagnostics table has no rows to query.
When this WOULD be correct
This option would be correct if the question stated that the workspace retention period was explicitly set to 1 hour and the query was run after that period, causing data to be deleted.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓The logs are written to resource-specific tables instead of AzureDiagnostics.Correct answer▾
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.
✗The storage account cannot send logs to Log Analytics when public network access is disabled.Wrong answer — click to see why▾
Why this is wrong here
The question states that the diagnostic setting was changed, not that public network access was disabled. AzureDiagnostics table is used for resource-specific logs only when the diagnostic setting sends logs to the legacy Azure Diagnostics mode; changing to resource-specific tables causes logs to go to separate tables, not AzureDiagnostics.
★ When this WOULD be the correct answer
This would be correct if the question described a scenario where a storage account has public network access disabled (e.g., using a private endpoint) and the diagnostic setting is configured to send logs to a Log Analytics workspace. In that case, network isolation would prevent log delivery, resulting in no rows in AzureDiagnostics.
Why candidates choose this
Candidates may confuse network restrictions with log routing changes, assuming that disabling public access blocks all log flow, but Azure Diagnostics can still send logs over private links or via the Azure backbone network.
✗The diagnostic setting only sends metrics, not logs, to the workspace.Wrong answer — click to see why▾
Why this is wrong here
The diagnostic setting explicitly includes 'send to Log Analytics' for logs, not just metrics. The question states the setting was changed to send logs to a Log Analytics workspace, so option C is incorrect because logs are being sent.
★ When this WOULD be the correct answer
This option would be correct if the diagnostic setting was configured to send only metrics (e.g., 'AllMetrics') to the Log Analytics workspace, and the query was for log data. For example, a question where the setting exports only performance counters and no log categories.
Why candidates choose this
Candidates may confuse the diagnostic setting's ability to send both metrics and logs, or assume that a change to the setting might have inadvertently disabled log collection, leading them to think only metrics are sent.
✗The workspace retention period automatically deletes all records after one hour.Wrong answer — click to see why▾
Why this is wrong here
The workspace retention period does not automatically delete records after one hour; the default retention is 30 days (or longer), and the question's scenario involves a change in diagnostic setting, not retention.
★ When this WOULD be the correct answer
This option would be correct if the question stated that the workspace retention period was explicitly set to 1 hour and the query was run after that period, causing data to be deleted.
Why candidates choose this
Candidates may confuse the concept of retention period with the immediate absence of data, assuming that a short retention explains why no rows are returned, especially if they overlook the diagnostic setting change.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Customer-Managed Keys (CMK) for Storage Encryption
Key term
Storage account
A cloud storage account is a container that holds a set of cloud storage services and their data, providing a unique namespace and access policies for storing and managing unstructured data.
Key term
Diagnostic setting
A Diagnostic setting is a configuration in Azure that controls where and how resource logs and metrics are collected, stored, and streamed for monitoring and analysis.
About these practice questions
One of 1,049 original AZ-104 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.