Microsoft Azure Data FundamentalsDescribe an analytics workload on AzureHard
A small startup is building its first analytics solution on Azure. They have a limited budget and currently process data in batches nightly. They anticipate gradual growth but need a cost-effective way to store and analyze structured data. Which Azure Synapse Analytics pricing model would be most suitable for their initial setup and future scaling while managing costs?
- ADedicated SQL pool with pause/resume functionality
- BDedicated SQL pool with high Data Warehouse Units (DWUs)
- CUsing Azure Databricks for all data storage and analysis
- DServerless SQL pool for all analytical queries
Show answer & explanationAnswer & explanation
Correct answer: A. Dedicated SQL pool with pause/resume functionality
A dedicated SQL pool with pause/resume functionality allows the startup to only pay for compute resources when they are actively running their nightly batch processes, significantly reducing costs during idle periods, while still providing the performance of a dedicated data warehouse when needed.
Why the other options are wrong
- B. A high DWU dedicated SQL pool would be expensive for a startup with a limited budget, especially if not utilized 24/7.
- C. Azure Databricks is a powerful big data analytics platform, but it's typically more expensive than a dedicated SQL pool for structured data warehousing and might be overkill for a startup's initial batch processing needs, especially if they are primarily focused on structured data.
- D. While serverless SQL pool is cost-effective for ad-hoc queries, it might not offer the same consistent performance or features as a dedicated data warehouse for all structured analytical needs as the startup grows, and the question implies a data warehouse solution.
Azure Synapse Dedicated SQL Pool Pause/Resume
A cost-saving feature for Azure Synapse Analytics dedicated SQL pools that allows users to suspend compute resources when not in use and resume them when needed, paying only for storage during paused periods.
- Compute resources are billed hourly when active.
- Storage is billed continuously regardless of compute state.
- Ideal for development/test environments or batch-oriented workloads with idle periods.
Memory trick: Pause your pool to save your 'dolla' bills.