App Service diagnostics and logging in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Enable Application Logging for Azure App Service

You run the following Azure CLI command to enable application logging for your App Service. What is the expected output?

Azure

az webapp log config --name MyAppService --resource-group MyResourceGroup --application-logging true

A

{
  "applicationLogs": {
    "fileSystem": {
      "level": "Information"
    }
  },
  "detailedErrorMessages": null,
  "failedRequestsTracing": null,
  "httpLogs": null
}

B

{
  "applicationLogs": {
    "fileSystem": {
      "level": "Error"
    }
  }
}

C ERROR: The command requires a log level to be specified when enabling application logging.

D CommandNotFoundError: az webapp log config is not recognized

💡 Hint

Check if the command requires a log level parameter when enabling application logging.

The Azure CLI command to enable application logging requires specifying the log level (e.g., Information, Error). Omitting it causes an error.

🧠 Conceptual

intermediate

Purpose of Failed Request Tracing in App Service

What is the main purpose of enabling Failed Request Tracing in Azure App Service diagnostics?

A To capture detailed logs of HTTP requests that fail, helping diagnose issues like 404 or 500 errors.

B To automatically restart the App Service when a failure occurs.

C To increase the maximum number of concurrent connections allowed.

D To enable real-time monitoring of CPU and memory usage.

💡 Hint

Think about what 'failed request' means in web applications.

Failed Request Tracing captures detailed information about HTTP requests that fail, which helps developers find the root cause of errors.

❓ Troubleshoot

advanced

Diagnosing Missing Logs in Azure App Service

You enabled application logging to the file system on your Azure App Service, but no logs appear in the LogFiles directory. What could be the cause?

A The Azure CLI command to enable logging was run without specifying the resource group.

B The application logging level is set to Verbose, which disables logs.

C The LogFiles directory is only created when HTTP logging is enabled.

D The App Service plan is on a Free tier, which does not support file system logging.

💡 Hint

Consider the limitations of different App Service plans.

File system logging is not supported on Free or Shared tiers of App Service plans. You must use Basic or higher tiers.

🔀 Workflow

advanced

Order of Steps to Enable and View HTTP Logs in Azure App Service

Arrange the steps in the correct order to enable HTTP logging and view the logs for an Azure App Service.

A 3,1,2,4

B 1,3,2,4

C 1,2,3,4

D 2,1,3,4

💡 Hint

Think about enabling logging before generating traffic and then accessing logs.

First enable logging, then generate traffic to create logs, then access and download logs for review.

✅ Best Practice

expert

Best Practice for Retaining Logs in Azure App Service

What is the best practice to ensure long-term retention and analysis of logs generated by Azure App Service?

A Send logs to Azure Blob Storage or Azure Monitor for centralized storage and analysis.

B Enable file system logging and rely on the default retention period.

C Configure streaming logs only and monitor them live without saving.

D Manually download logs daily from the LogFiles directory.

💡 Hint

Think about scalable, automated log storage solutions.

Sending logs to Azure Blob Storage or Azure Monitor allows centralized, durable storage and advanced analysis capabilities.