Which Azure Monitor Features Provide Synthetic Transaction Monitoring for App1?
You have an Azure subscription. The subscription contains a tiered app named App1 that is distributed across multiple containers hosted in Azure Container Instances. You need to deploy an Azure Monitor monitoring solution for App1. The solution must meet the following requirements: • Support using synthetic transaction monitoring to simulate real user interactions and identify UI failures. • Minimize development effort. What two features can you include in the solution? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Community Insight
The question tests whether you can identify the only Azure Monitor feature that generates synthetic user interactions (Application Insights availability tests) plus the low-effort host for multi-step tests (a Function App) — the trap is reaching for Container insights simply because App1 runs in containers.
Azure Monitor synthetic transaction monitoring for a multi-tier app spread across Azure Container Instances is delivered by Application Insights availability tests paired with a Function App that runs a custom multi-step test. This page explains why options B and C satisfy both the UI-failure detection and minimal-development-effort requirements.
Selecting Container insights because App1 is distributed across Azure Container Instances. Container insights only surfaces resource, memory, disk and restart telemetry for Kubernetes and Arc-enabled clusters, performs no browser-level or synthetic transaction monitoring, and does not cover ACI at all.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Azure Monitor Application Insights is the application performance monitoring service inside Azure Monitor, and its availability tests (URL ping and standard tests) are the only option here that performs synthetic transaction monitoring: they repeatedly call an endpoint from multiple regions and report availability, responsiveness and content/UI failures without any change to App1's code. Because App1 is a tiered app spread across multiple ACI containers, a single URL ping cannot reproduce a real user journey across tiers, so a Function App supplies the second piece — a timer-triggered custom availability test that chains requests and pushes results via TrackAvailability. Together they satisfy "simulate real user interactions and identify UI failures" while keeping development effort low, since you write a short function instead of building a monitoring pipeline. Estratech's comment captures the mechanism: "Availability tests repeatedly test an application from different locations".Why the Other Options Are Wrong
Log Analytics Workspace Insights reports the health, ingestion volume, cost and query usage of the workspace itself; it has no synthetic or browser-level capability and would not detect a broken UI flow. Container insights emits CPU, memory, disk, restart and log telemetry for AKS and Azure Arc-enabled Kubernetes, and Azure Container Instances is outside its supported scope — even where it applies it never simulates a user interaction. Azure Monitor Network Insights is a topology and connectivity view over NSGs, firewalls, load balancers and their metrics; it is useful for locating where a tiered app fails to connect, but it cannot identify UI failures. A Function App is not a monitoring service on its own: it is the execution host for the custom availability test, which only becomes a synthetic monitoring solution because it writes results into Application Insights — that is why the two features appear together.Community Comment Notes
Estratech selected B and C and explained that availability tests repeatedly exercise an application from different locations and report availability, responsiveness and failures, and that tests can be configured without modifying the monitored application, which is exactly the minimal-development argument. Mesloth pushed back on the Function App as conflicting with minimize development effort; the resolution is that a timer-triggered function calling TrackAvailability is a handful of lines of code, far cheaper than authoring and maintaining a legacy multi-step Visual Studio web test or a bespoke synthetic runner. Notably, no commenter defended Container insights or Network Insights for App1's UI failures, and none disputed that Application Insights is the only synthetic-capable option.Official Reference
Exam Strategy
Anchor on the verb in the requirement: "synthetic transaction" or "simulate user interactions" almost always maps to Application Insights availability tests, and "minimize development effort" disqualifies anything that requires writing full monitoring code. Once you fix Application Insights, eliminate the remaining options by asking which one can host a multi-step test across tiers rather than merely report resource metrics.
Frequently Asked Questions
Why isn't Container insights enough to detect App1's UI failures?
Container insights only reports resource, restart and log telemetry for Kubernetes and Arc-enabled clusters, and it does not even cover Azure Container Instances. It never simulates a user interaction, so it cannot surface UI failures.
How does a Function App keep development effort low for the synthetic test?
A timer-triggered function calls TrackAvailability() to send the multi-step result straight into Application Insights, so you write a few lines instead of building a custom synthetic monitoring runner.
Related Analysis
Practice All AZ-305 Questions
Access 95 questions with complete answers and detailed explanations.
View Full AZ-305 Practice Test →