Section-Based – Deploy and Manage Azure Compute Resources (AZ-104) question 2

[mrmumse]

I’m perplexed about the correct answer being “Enable Web Server logging feature” here. It’s more probable that the deployed code is causing the 500 error, rather than the web server. Therefore the developers would need to see the error thrown by the application code, rather than what the web server knows. I’ve worked with Azure App Service for quite some time and never used that logging, as the problem has always lied within the deployed code.

Please elaborate on the answer!

[Irene-TutorialsDojo]

Hi mrmumse,

Thank you for your question. The reason the correct answer is to “Enable Web Server Logging” is that HTTP 500 errors are often caused by issues at the server level, not just within the application code.

Web Server Logging captures detailed information about incoming requests and server responses, including any failures before the request reaches your application code. This is important because the error might not be directly in the application logic but in how the server handles requests, such as misconfigurations, timeouts, or resource issues.

While application logging is essential for catching errors within the application code, enabling web server logging helps you understand what happens at the server level and provides more context for troubleshooting.

In many cases, seeing the web server’s full request/response flow helps identify problems that application-level logs might miss. Therefore, it’s best to start with enabling Web Server Logging, and then you can dive into Application Logging if necessary.

Hope this helps! Please don’t hesitate to let us know if you have any further questions.

Cheers,

Irene @ Tutorials Dojo