You operate a Windows App Service hosting an ASP.NET Core app. During incidents, you need to tail application logs in real time. For compliance, you must also retain HTTP access logs for 30 days in Azure Storage. Long-term retention of application logs is not required. What should you configure?

The correct options address both requirements. Enabling Application Logging (File System) allows real-time log tailing via the Azure portal's Log Stream blade or the az webapp log tail CLI command, fulfilling the need for immediate troubleshooting without long-term retention. Setting the level to Warning is appropriate for incident response, focusing on critical issues. Enabling Web Server logging and configuring it to write to a blob storage container with a 30-day retention policy directly satisfies the compliance requirement for HTTP access logs. Web Server logging captures HTTP-related information, and Azure Storage provides the necessary retention. Incorrect options: Application Insights is primarily for application performance monitoring and telemetry, not for direct HTTP access log retention or real-time file system log tailing in this specific manner. Detailed Error Messages and Failed Request Tracing are for debugging specific request failures, not general HTTP access logs or real-time application log streaming. Enabling Application Logging (Blob) would store application logs in blob storage, but the Log Stream blade cannot directly tail logs from blob storage; it's designed for file system logs.