You have an ASP.Net Core application running in a Windows App Service.
The application generates log messages that should be stored for one week at least.
You need to enable a diagnostics logging and only store logs with the severity level of Warning or higher.
How should you configure the diagnostics logging? To answer, select the appropriate options from the drop-down menus.
You should enable the Application Logging (Blob) diagnostics logging. This setting can store logs generated by the application in a Blob Storage. You can access the application logs stored for more than one week.
You should also configure the severity level to Warning. You should use the Warning severity level to store only Warning, Error, and Critical log messages.
You should not enable the Application Logging (Filesystem) diagnostics logging. This setting saves the application log directly in the App Service filesystem. This option should be used only for debugging purposes because it is enabled for only 12 hours before turning itself off.
You should not enable the Detailed Error Messages diagnostics logging. This setting can store detailed error pages in HTML format that is hidden to clients using the application.
You should not enable the Web server logging (Storage) diagnostics logging. This setting can store raw HTTP request data from the webserver in a Blob Storage. You can use this setting in Windows App Services only.
You should not configure the severity level to Error. This severity level stores Error and Critical log messages. However, log messages with the Warning severity level will not be stored.
You should not configure the severity level to Information or Verbose. These severity levels store Warning, Error, and Critical log messages. However, they also store Info log messages for Information level, and also Trace for Verbose level, storing more log messages than necessary by the requirements.