While preparing for the AZ-305, many candidates struggle with monitoring strategy and diagnostic settings for Azure SQL in complex enterprise environments. In the enterprise world, this decision often hinges on balancing data residency, governance, operational visibility, and integration complexity. Let’s drill into a simulated hybrid monitoring scenario.
The Scenario #
Contoso Pharmaceuticals manages a critical Azure SQL database named RxCoreDB located in the East US region. To align with corporate governance and layered monitoring strategy, RxCoreDB has an existing diagnostic setting named DiagSet1 configured to archive SQLInsights logs to storage account StorAcc1 and stream logs to Azure Monitor workspace LogAnalytics1.
Contoso is now exploring expanding their diagnostics footprint to meet compliance and operational requirements:
Key Requirements #
Evaluate whether the following statements are valid in this Azure SQL diagnostic context:
-
It is possible to add a new diagnostic setting to archive SQLInsights logs to a different storage account
StorAcc2. -
It is possible to add a new diagnostic setting to send SQLInsights logs to a different Log Analytics workspace
LogAnalytics2. -
It is possible to add a new diagnostic setting to send SQLInsights logs to an Event Hub
EventHub1.
The Options #
- A) Yes, all three additional diagnostic settings are supported and can be added concurrently.
- B) No, adding multiple diagnostic settings for SQLInsights logs with different destinations is not supported.
Correct Answer #
A) Yes, all three additional diagnostic settings are supported and can be added concurrently.
Step-by-Step Winning Logic #
Azure SQL Database diagnostic settings support multiple concurrent configurations, each sending telemetry to distinct destinations. This flexibility allows organizations to meet diverse governance needs:
- Storage accounts provide durable archival storage for audit trails or legal compliance.
- Log Analytics workspaces enable rich querying and integration with Azure Monitor for operational insights.
- Event Hubs facilitate streaming diagnostics to external SIEM or third-party monitoring tools.
This aligns perfectly with the Well-Architected Framework pillars of Operational Excellence (monitoring transparency) and Security & Compliance (governed telemetry).
馃拵 The Architect’s Deep Dive: Why Options Fail #
The Traps (Distractor Analysis) #
-
Why not Option B?
The misconception is that Azure SQL only supports a single diagnostic setting per resource, but in fact multiple diagnostic settings can co-exist to route data to multiple sinks. -
Options C and D
These are placeholders without meaning in this scenario.
The Architect Blueprint #
Illustrating diagnostic data flows from Azure SQL to multiple sinks.
graph TB
SQL[Azure SQL Database: RxCoreDB]
SQL -->|Logs: SQLInsights| StorAcc1[Storage Account: StorAcc1]
SQL -->|Logs: SQLInsights| LogAnalytics1[Log Analytics Workspace: LogAnalytics1]
SQL -->|Logs: SQLInsights| StorAcc2[Storage Account: StorAcc2]
SQL -->|Logs: SQLInsights| LogAnalytics2[Log Analytics Workspace: LogAnalytics2]
SQL -->|Logs: SQLInsights| EventHub1[Event Hub: EventHub1]
style SQL fill:#5C2D91,stroke:#333,color:#fff
style StorAcc1 fill:#0078D4,stroke:#333,color:#fff
style StorAcc2 fill:#0078D4,stroke:#333,color:#fff
style LogAnalytics1 fill:#00B0F0,stroke:#333,color:#fff
style LogAnalytics2 fill:#00B0F0,stroke:#333,color:#fff
style EventHub1 fill:#732C7B,stroke:#333,color:#fff
Diagram Note: Azure SQL database sends diagnostic logs concurrently to multiple different destinations, facilitating layered monitoring and compliance.
The Decision Matrix (Expert Level) #
| Option | Est. Complexity | Est. Monthly Cost | Pros | Cons |
|---|---|---|---|---|
| A | Medium | Moderate | Supports multi-sink routing and layered telemetry | Slightly more management overhead |
| B | Low | Low | Simpler, single sink management | Limited flexibility, governance risk |
| C/D | N/A | N/A | N/A | N/A |
Cost Explanation:
Each diagnostic setting consumes storage and data ingestion resources. Using multiple storage accounts and Log Analytics workspaces increases total costs depending on ingested volume and retention. Event Hub streaming costs vary with streaming volume and consumer throughput units.
Real-World Practitioner Insight #
Exam Rule #
“For official AZ-305 scenarios, remember that Azure diagnostic settings support multiple concurrent configurations to different targets when multiple monitoring and compliance streams are needed.”
Real World #
“At Contoso Pharmaceuticals, segregating logs into separate storage accounts and Log Analytics workspaces allowed specialized teams (Security, Compliance, Operations) to independently control and analyze logs without cross-team interference鈥攂oosting governance in hybrid cloud environments powered by Azure Arc-connected servers.”