HOTSPOT
You manage an Azure Web Site named contosoweb.
Some users report that they receive the following error when they access contosoweb: “http
Status 500.0 – Internal Server Error.”
You need to view detailed diagnostic information in XML format.
Which option should you enable? To answer, select the appropriate option in the answer area.
Answer: 
Explanation:
I don´t get it. 500 is a custom error, it shows me no detail. I think the right answer should be enabling detailed error messages.
Anybody?
Failed Request Tracing
http://azure.microsoft.com/en-us/documentation/articles/web-sites-monitor/#webendpointstatus
Pras, sorry about insisting but:
Cause of HTTP 500 Errors
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site’s server but the server could not be more specific on what the exact problem is.
Log File Type: Detailed Error Logging
Detailed Error Information: Includes information about the error such as Module, Handler, Error Code, and Requested URL.
Links and More Information: Provides additional summary information about the error and may also include links to other resources such as Microsoft Knowledge Base articles.
You really don´t think that there is no chance of detailed error messages be the right answer?
http://azure.microsoft.com/en-us/documentation/articles/web-sites-monitor/#webendpointstatus
Failed Request Tracing produces an XML document….
“Failed request tracing produces an XML document that contains a trace of which modules the request passed through in IIS, details returned by the module, and the time the module was invoked. This information can be used to isolate which component the failure occurred in.”
The detailed error logs are available in .htm format while Failed Error logs are available in XML format
Failed Request Traces – /LogFiles/W3SVC#########/. This folder contains an XSL file and one or more XML files. Ensure that you download the XSL file into the same directory as the XML file(s) because the XSL file provides functionality for formatting and filtering the contents of the XML file(s) when viewed in Internet Explorer.
Detailed Error Logs – /LogFiles/DetailedErrors/. This folder contains one or more .htm files that provide extensive information for any HTTP errors that have occurred.
Only “failed request tracing” gives XML log
But in a real live situation I can’t figure out any reasons to not activate all logs. Error 500 is just a generic error : I know there is an issue, I don’t know where
I don’t care the log is an XML format, who cares anyway?. I just need to solve the issue
This is a very bad question
I just read this bit on https://azure.microsoft.com/en-us/documentation/articles/web-sites-monitor/
“Important: Detailed Error Messages and Failed Request Tracing place significant demands on a web app. We recommend turning off these features once you have reproduced the problem(s) that you are troubleshooting.”
Hey fred! maybe your notepad++ can only use XML 😉
Failed Request Tracing
Agree,
Correct Answer= Failed Request Tracing
The directory structure that the logs are stored in is as follows:
Application logs – /LogFiles/Application/. This folder contains one or more text files containing information produced by application logging.
Failed Request Traces – /LogFiles/W3SVC#########/. This folder contains an XSL file and one or more XML files. Ensure that you download the XSL file into the same directory as the XML file(s) because the XSL file provides functionality for formatting and filtering the contents of the XML file(s) when viewed in Internet Explorer.
Detailed Error Logs – /LogFiles/DetailedErrors/. This folder contains one or more .htm files that provide extensive information for any HTTP errors that have occurred.
Web Server Logs – /LogFiles/http/RawLogs. This folder contains one or more text files formatted using the W3C extended log file format.
Deployment logs – /LogFiles/Git. This folder contains logs generated by the internal deployment processes used by Azure web apps, as well as logs for Git deployments.
https://azure.microsoft.com/en-us/documentation/articles/web-sites-enable-diagnostic-log/