You develop and deploy a web app to Azure App Service. The Azure App Service uses a Basic plan in a single region. You need to capture the telemetry. Which three actions should you perform? Each…

Upgrading to an Azure App Service Premium plan is not required for capturing basic telemetry or enabling Profiler; the Basic plan, coupled with Application Insights, is sufficient.

Enabling remote debugging is used for interactive code debugging and troubleshooting, not for continuous, automated telemetry capture in a production environment.

Enabling Profiler within Application Insights allows for deep performance analysis by collecting detailed traces of your application's execution. This helps identify bottlenecks and slow code paths, providing crucial telemetry about application performance.

After enabling or configuring Application Insights, including site extensions or Profiler, restarting the app service app is often necessary. This action ensures that the App Service runtime picks up the new configuration and properly initializes the Application Insights agents for telemetry collection.

The Snapshot Debugger captures execution snapshots upon exceptions for post-mortem analysis, which is distinct from general performance and usage telemetry collected by Profiler and Application Insights.

Enabling Application Insights site extensions is the primary method for integrating Application Insights with an Azure App Service without modifying application code. This extension injects the necessary SDKs and agents into the app service environment, allowing for automatic collection of performance, dependency, and request telemetry.

The Always On setting prevents the app from unloading due to inactivity, which helps with responsiveness, but it does not directly enable or configure the capture of telemetry data.