Microsoft Azure Data FundamentalsDescribe how to work with relational data on AzureHard
A company is considering migrating its on-premises PostgreSQL database to Azure. The database experiences highly fluctuating workloads, with periods of intense activity followed by long periods of inactivity. The company wants a cost-effective solution that automatically scales compute resources up and down based on demand, and pauses billing during inactive periods. Which Azure Database for PostgreSQL deployment option should they choose?
- AAzure Database for PostgreSQL - Serverless
- BAzure Database for PostgreSQL - Single Server
- CAzure Database for PostgreSQL - Flexible Server
- DAzure Database for PostgreSQL - Hyperscale (Citus)
Show answer & explanationAnswer & explanation
Correct answer: A. Azure Database for PostgreSQL - Serverless
Azure Database for PostgreSQL - Serverless is specifically designed for intermittent and unpredictable workloads by automatically scaling compute resources and pausing billing during periods of inactivity. This makes it highly cost-effective for the described scenario.
Why the other options are wrong
- B. Single Server is a fixed-size deployment option that does not offer automatic compute scaling or pausing, leading to higher costs during inactive periods.
- C. Flexible Server offers more control and cost optimization features than Single Server (like stop/start), but it does not provide automatic, on-demand compute scaling to zero and pausing billing during inactivity like the Serverless option.
- D. Hyperscale (Citus) is designed for large-scale, distributed databases requiring extreme horizontal scaling, not primarily for cost optimization with fluctuating, intermittent workloads.
Azure DB for PostgreSQL Serverless
A deployment option for Azure Database for PostgreSQL that automatically scales compute capacity based on demand and pauses billing during periods of inactivity, optimized for intermittent and unpredictable workloads.
- Automatic compute scaling based on workload.
- Pauses billing during inactivity.
- Cost-effective for intermittent workloads.
- Ideal for dev/test, infrequent applications, and bursty workloads.
Memory trick: Serverless for savings on sporadic demand.