You have an Azure web app named webapp1. Users report that they often experience HTTP 500 errors when they connect to webapp1. You need to provide the developers of webapp1 with real-time access to…

The correct answer is A. From webapp1, enable Web server logging. Raw HTTP request data is provided by Web server logging and the question mentions 500 error You need to catch connection error. When the connection fails it happens on web server, not within application. You can do it opening the web application -> Application Service logs ->…

Submitted by fernanda_arg· Mar 4, 2026Monitor and maintain Azure resources

Question

You have an Azure web app named webapp1. Users report that they often experience HTTP 500 errors when they connect to webapp1. You need to provide the developers of webapp1 with real-time access to the connection errors. The solution must provide all the connection error details. What should you do first?

Options

AFrom webapp1, enable Web server logging
BFrom Azure Monitor, create a workbook
CFrom Azure Monitor, create a Service Health alert
DFrom webapp1, turn on Application Logging

How the community answered

(29 responses)

A
62% (18)
B
7% (2)
C
21% (6)
D
10% (3)

Explanation

Raw HTTP request data is provided by Web server logging and the question mentions 500 error You need to catch connection error. When the connection fails it happens on web server, not within application. You can do it opening the web application -> Application Service logs -> Web server logging (there are multiple switches there). You can also see the errors live going to "Log stream" pane. Web server logging Windows App Service file system or Azure Storage blobs Raw HTTP request data in the W3C extended log file format. Each log message includes data such as the HTTP method, resource URI, client IP, client port, user agent, response code, and so on.

Community Discussion

No community discussion yet for this question.

Full AZ-104 Practice