Correct Answer: A Raw HTTP request data is provided by Web server logging and the question mentions 500 error codes. 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.

I think A as well. You need to catch connection error. When the connection fails it happens on web server, not within application. You can do it openining 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

I'm beginner in Azure but skilled in middleware administration. In my opinion you have to check application logs as web server logs will indicate only HTTP 500 response (internal server error) , nothing else. Is in the backend application log where you will get more info about the error. So D would be correct

A is right

Answer is D. There isn't even an option for web server logging in the portal.

Correct Anser is: A From webapp1, enable Web server logging

Correct Answer: A https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-performance-degradation#enable-web-server-diagnostics

Given answer is correct, see; https://techcommunity.microsoft.com/t5/apps-on-azure-blog/troubleshooting-azure-app-service-apps-using-web-server-logs/ba-p/392329 "Oftentimes, the best way to start troubleshooting a web application is to check the web server logs. Web servers log each request that they process, and by checking the server logs, you can often find out details about why things went wrong. Particularly, you want to pay attention to a couple of different fields in the log file; the HTTP status code and the HTTP sub-status code. In your server logs, these are labeled as sc-status and sc-substatus ."

D. From webapp1, turn on Application Logging. To provide the developers with real-time access to the connection errors, you should first enable Application Logging for the web app. This will enable the logging of detailed information about the application, including any connection errors, to the file system, which the developers can then access to troubleshoot the issue. After Application Logging has been enabled, you may also consider additional monitoring and alerting solutions, such as Azure Monitor or Service Health alerts, to provide ongoing visibility into the health and performance of the web app.

I don't like this question. HTTP 500 is an internal server error, not really a connection error. In my world this is mostly caused by the application code, so I would look into the application logs first. But as this question explicitly asks about connection errors, I am just confused.

i think answer should be "D" 'Application Log' How do I check my 500 error in Azure portal? Check logs Open your bot in the Azure portal. Open the App Service Settings / All App service settings page to see all service settings. Open the Monitoring / Diagnostics Logs page for the app service. Ensure that Application Logging (Filesystem) is enabled. ... Switch to the Monitoring / Log Stream page.

Answer is D.. Application logging... have checked there is no option like web server logging in the application service..

out of the four options, realtime error details will be: A. From webapp1, enable Web server logging

500 error can be pretty much anything either on a webserver or within the app itself. Webserver logs are good to investigate but definitely does not provide all error logs that are needed. There is no correct answer here, but A + D is the closest.

Think D is right. HTTP 500 is more of an application error than a web server connectivity error

Correct Answer: A

Web server logging is correct