The correct answers are Enable Application Insights integration for the App Service, Create an Application Insights resource in the subscription, and Instrument the ASP.NET application to send telemetry to Application Insights.

Enable Application Insights integration for the App Service configures the platform to surface App Service metrics and to link the running app to an Application Insights resource. Turning on integration in the portal or via deployment templates makes it easy to route App Service level telemetry and to inject the connection string into the app settings.

Create an Application Insights resource in the subscription is required because Application Insights is the service that stores, analyzes, and visualizes telemetry. The resource provides the connection string or instrumentation key that the integration or the SDK uses to send data to Azure Monitor.

Instrument the ASP.NET application to send telemetry to Application Insights means adding the Application Insights SDK or using the built in ASP.NET Core telemetry features so requests, exceptions, dependencies, and custom events are emitted. Platform integration can capture some metrics but application level traces and dependency data require proper instrumentation.

Create a Data Collection Rule is not correct because data collection rules are for the Azure Monitor agent and scenarios like virtual machines and Kubernetes. They are not the standard mechanism for collecting telemetry from App Service hosted ASP.NET Core apps.

Install a site extension on the App Service is not required for current Application Insights collection. Older site extensions existed but the supported approaches are to enable App Service integration or to instrument the application with the SDK, so the site extension is not the recommended path for modern deployments.

Full AWS Practitioner Certification Question