A ferry team enables App Service diagnostic logging and claims their Domain 4 monitoring work is complete. How should a developer correct that claim?
Select an answer to reveal the explanation.
Short Explanation
App Service logs are the ferry terminal’s own CCTV—great for host-level clues. Application Insights is the fleet telemetry system with metrics, traces, and “is the route up?” tests. Flipping on host diagnostics does not finish Domain 4 for you.
Full Explanation
App Service diagnostic logging is the host’s own web-server and application log stream. Domain 4 monitoring on AZ-204 still centers on Application Insights for metrics, distributed traces, dependency tracking, and availability tests. The ferry team cannot claim Domain 4 work is complete merely by flipping on App Service diagnostics—CCTV at the terminal is not the whole fleet telemetry system.
Diagnostic logging does not fully replace Application Insights capabilities. Diagnostics are not “only for Container Apps,” and App Service sites do not need Azure Monitor Agent on VMs as a substitute for App Service logging. Enabling web-server logs does not automatically provision an Application Insights resource or share an instrumentation key.
Exam caveat: you often use both: App Service diagnostics for platform/request logs, Application Insights for application performance monitoring. Know which blade configures which signal on the exam.
Operational check: with diagnostics already on, create or link Application Insights, emit a custom trace and a dependency call, run an availability test against the ferry site, and show that those Domain 4 signals appear in Insights—not only in App Service log files.