You want to gather logs from a large number of Windows Server 2016 computers using Azure Log Analytics. You are configuring an Azure Resource Manager template to deploy the Microsoft Monitoring…

Question

Options

• AWorkspaceID
• BAzureADApplicationID
• CWorkspaceKey
• DStorageAccountKey

• A
  84% (27)
• B
  9% (3)
• D
  6% (2)

Explanation

Explanation

When deploying the Microsoft Monitoring Agent (MMA) via an ARM template, the agent must authenticate and connect to your specific Log Analytics workspace - this requires both the WorkspaceID (to identify which workspace to send logs to) and the WorkspaceKey (a shared secret that authenticates the connection), making both A and C essential components of the template configuration.

Option B (AzureADApplicationID) is incorrect because the MMA uses workspace-based authentication, not Azure Active Directory application credentials - AAD App IDs are used for service principals and OAuth-based authentication flows, which are unrelated to this agent deployment.

Option D (StorageAccountKey) is incorrect because Log Analytics does not require a storage account for agent-based log collection - storage account keys are relevant for diagnostics settings that route logs through Azure Storage, which is a different architecture.

Memory Tip: Think of it like logging into a service - you always need a username (WorkspaceID = who you're connecting to) and a password (WorkspaceKey = proof you're allowed in). Everything else (AAD, Storage) belongs to different Azure services and shouldn't be confused with the MMA's simple workspace-based connection model.

No community discussion yet for this question.