You have an Azure Storage account named `storeprodlogs`. You need to configure diagnostic logging to collect read, write, and delete transaction logs for the Blob service. The configuration must meet the following requirements:
- Allow operations teams to analyze the transaction logs using Kusto Query Language (KQL) queries.
- Archive the logs to a separate storage account named `storearchive` for long-term retention.
Which two actions should you perform? (Select two.)
- Create the diagnostic setting at the Blob service level (`storeprodlogs/blobServices/default`).Answer
- BCreate the diagnostic setting at the Storage account level (`storeprodlogs`).
- Select both a Log Analytics workspace and the `storearchive` storage account as destinations in the diagnostic setting.Answer
- DConfigure the 365-day log retention policy within the diagnostic setting when targeting the Log Analytics workspace.
- EAssign the Storage Blob Data Contributor role to the Azure Monitor service principal on the `storearchive` storage account.
Answer
To meet the requirements, you must create the diagnostic setting at the Blob service level (`storeprodlogs/blobServices/default`) and select both a Log Analytics workspace and the `storearchive` storage account as the export destinations.
To capture Blob transaction logs, the diagnostic setting must be created on the Blob service sub-resource (`storeprodlogs/blobServices/default`). Additionally, to allow KQL analysis and long-term archiving, both a Log Analytics workspace and a storage account must be specified as export destinations.
Step-by-Step Solution
Key Concept
Configuring service-level diagnostic settings for Azure Storage and routing logs to multiple diagnostic destinations.