Your ASP.NET Core Web API uses Application Insights for telemetry and tracks dependencies to a non-SQL Server database. To enable proper dependency tracking for that database, which two dependency telemetry properties should you set?

To ensure proper dependency tracking for a non-SQL Server database in Application Insights, you need to set Telemetry.Id and Telemetry.Context.Operation.Id. Telemetry.Id uniquely identifies the dependency call itself, allowing Application Insights to correlate it with other telemetry items. Telemetry.Context.Operation.Id links the dependency call to the overall operation (e.g., a web request) that initiated it, enabling end-to-end transaction tracing. Without these, Application Insights cannot accurately reconstruct the flow of requests and dependencies, especially for custom or non-standard data sources. Telemetry.Name describes the dependency type or target, but doesn't provide correlation. Telemetry.Context.Cloud.RoleInstance identifies the specific instance of your application, not the dependency itself. Telemetry.Context.Session.Id tracks user sessions, which is not directly relevant for dependency correlation.