Microsoft Azure Developer Associate AZ-204 practice test

An app must store relational state and perform transactions across multiple tables with T-SQL support. Which Azure data service should the developer choose?

Trap 1: Azure Queue Storage

Queue Storage is for messaging, not relational state.

Trap 2: Azure Cache for Redis

Redis is an in-memory cache and not the primary relational database.

Trap 3: Azure Blob Storage

Blob Storage is object storage and does not provide relational transactions.

A
Azure Queue Storage
Why wrong: Queue Storage is for messaging, not relational state.
B
Azure SQL Database
Azure SQL Database supports relational schema, T-SQL, and transactions.
C
Azure Cache for Redis
Why wrong: Redis is an in-memory cache and not the primary relational database.
D
Azure Blob Storage
Why wrong: Blob Storage is object storage and does not provide relational transactions.

Question 2mediummultiple choice

You are monitoring an Azure App Service using Application Insights. You notice that the server response time is high for certain requests. You need to drill down to see which external dependencies (like databases or APIs) are causing the delay. Which Application Insights feature should you use?

Trap 1: Live Metrics

Live Metrics provides real-time monitoring of metrics and requests but does not offer detailed dependency breakdowns.

Trap 2: Application Map

Application Map visualizes the dependencies and flow between components but does not show detailed timing of each dependency call.

Trap 3: Snapshot Debugger

Snapshot Debugger takes snapshots of exception code; it is not used for analyzing slow responses.

A
Live Metrics
Why wrong: Live Metrics provides real-time monitoring of metrics and requests but does not offer detailed dependency breakdowns.
B
Application Map
Why wrong: Application Map visualizes the dependencies and flow between components but does not show detailed timing of each dependency call.
C
Profiler
Profiler captures per-request execution traces, including time spent in external dependencies, helping identify which dependency is slow.
D
Snapshot Debugger
Why wrong: Snapshot Debugger takes snapshots of exception code; it is not used for analyzing slow responses.

Read the full NAT/PAT explanation →

Question 3mediummulti select

Which TWO services can be used to implement a publish-subscribe messaging pattern in Azure?

Trap 1: Azure Storage Queues

Storage Queues are for point-to-point messaging.

Trap 2: Azure Event Hubs

Event Hubs is for event streaming, not pub-sub.

Trap 3: Azure Queue Storage

Queue Storage is for point-to-point messaging.

A
Azure Storage Queues
Why wrong: Storage Queues are for point-to-point messaging.
B
Azure Event Hubs
Why wrong: Event Hubs is for event streaming, not pub-sub.
C
Azure Service Bus Topics
Service Bus Topics support pub-sub with subscriptions.
D
Azure Event Grid
Event Grid is a pub-sub event routing service.
E
Azure Queue Storage
Why wrong: Queue Storage is for point-to-point messaging.

Question 4easymultiple choice

You need to monitor the CPU utilization of an Azure VM in real-time and set up an alert when it exceeds 90%. Which Azure Monitor feature should you use?

Trap 1: Log Analytics Workspace

Incorrect. Log Analytics is for analyzing log data, not real-time metrics; it adds latency.

Trap 2: Application Insights

Incorrect. Application Insights focuses on application performance monitoring, not VM-level host metrics.

Trap 3: Azure Monitor for VMs

Incorrect. Azure Monitor for VMs gives health summaries but the primary metric alert creation is through Metrics Explorer.

A
Log Analytics Workspace
Why wrong: Incorrect. Log Analytics is for analyzing log data, not real-time metrics; it adds latency.
B
Metrics Explorer
Correct. Metrics Explorer provides near real-time platform metrics and supports creating metric alerts.
C
Application Insights
Why wrong: Incorrect. Application Insights focuses on application performance monitoring, not VM-level host metrics.
D
Azure Monitor for VMs
Why wrong: Incorrect. Azure Monitor for VMs gives health summaries but the primary metric alert creation is through Metrics Explorer.

Question 5easymultiple choice

You are monitoring an Azure web application with Application Insights. You notice a sudden increase in the number of failed requests. You want to be notified automatically when such anomalies occur, without manually setting static thresholds. Which Application Insights feature should you use?

Trap 1: Create a metric alert on the 'failed requests' metric with a static…

A static threshold alert would require you to set a fixed number, which may not adapt to normal variations. Smart Detection is better for anomaly detection.

Trap 2: Use Log Analytics to run a query every 5 minutes and trigger an…

Log Analytics queries can be used in log alerts, but they require you to define the query and threshold manually. Smart Detection is automated.

Trap 3: Create an availability test that periodically pings the application.

Availability tests monitor the endpoint's uptime and response, but they do not analyze anomalies in failed request patterns from real user traffic.

A
Create a metric alert on the 'failed requests' metric with a static threshold.
Why wrong: A static threshold alert would require you to set a fixed number, which may not adapt to normal variations. Smart Detection is better for anomaly detection.
B
Enable Smart Detection for failure anomalies.
Correct. Smart Detection automatically analyzes telemetry and alerts on anomalous patterns, such as a sudden spike in failed requests.
C
Use Log Analytics to run a query every 5 minutes and trigger an action.
Why wrong: Log Analytics queries can be used in log alerts, but they require you to define the query and threshold manually. Smart Detection is automated.
D
Create an availability test that periodically pings the application.
Why wrong: Availability tests monitor the endpoint's uptime and response, but they do not analyze anomalies in failed request patterns from real user traffic.

Question 6mediummultiple choice

You are monitoring an Azure web app using Application Insights. You need to create a query that returns the average duration of requests for each HTTP method (GET, POST, etc.) over the last hour, sorted by duration. Which Kusto query should you use?

Trap 1: requests | summarize avg(duration) by method | order by…

Incorrect. This query lacks a time filter and would return data for the entire retention period, not just the last hour.

Trap 2: requests | summarize avg(duration) by method | sort by method asc

Incorrect. This query lacks a time filter and sorts by method name, not by average duration.

Trap 3: requests | where timestamp > ago(1h) | summarize avg(duration) by…

Incorrect. Correctly filters by time but sorts by method name instead of average duration.

A
requests | summarize avg(duration) by method | order by avg_duration desc
Why wrong: Incorrect. This query lacks a time filter and would return data for the entire retention period, not just the last hour.
B
requests | summarize avg(duration) by method | sort by method asc
Why wrong: Incorrect. This query lacks a time filter and sorts by method name, not by average duration.
C
requests | where timestamp > ago(1h) | summarize avg(duration) by method | order by avg_duration desc
Correct. Filters to the last hour, summarizes by method with average duration, and orders descending by that average.
D
requests | where timestamp > ago(1h) | summarize avg(duration) by method | sort by method
Why wrong: Incorrect. Correctly filters by time but sorts by method name instead of average duration.