You plan to deploy the Azure Monitor agent to 100 on-premises servers that run Windows Server. Which parameters should you provide when you install the agent?

Client ID and secret of an Azure service principal are used for programmatic access to Azure resources, not for agent installation to connect to a Log Analytics workspace.

Azure Storage account details are for storing diagnostic data or backups, not for the Azure Monitor agent's primary data ingestion destination.

A connection string for an Azure SQL database is irrelevant for installing the Azure Monitor agent and connecting it to a Log Analytics workspace.

The Azure Monitor agent (AMA) requires an Azure Log Analytics workspace to send its collected data, such as logs and performance metrics. When deploying the agent, you must specify the Workspace ID and the primary or secondary key of the Log Analytics workspace. These credentials allow the agent to securely authenticate and establish a connection to the designated workspace to ingest monitoring data.