AZ-305 Practice Question 74: SQL Serverless Auto Pause

Microsoft Azure Solutions Architect Expert (AZ-305) · Test 8 · question 4 of 10

Data Storage Solutionseasy

A single Azure SQL Database supports an internal reporting tool that is queried in short bursts a few times per day and is idle the rest of the time. Usage volume is unpredictable and the business wants to pay only for compute while the database is actually active, accepting a short delay when a new session resumes the database from an idle state. Which configuration should the architect recommend?

Select one answer
Show answer and explanation

Answer:

  • B. The General Purpose service tier with the serverless compute tier, configured to auto-pause after a period of inactivity.

The serverless compute tier, available in the General Purpose service tier, automatically scales compute based on workload demand and pauses the database during inactive periods, billing only for storage while paused and resuming automatically (with a warm up delay) when activity returns. That matches an intermittent, unpredictable workload that can tolerate a brief resume delay.

Hyperscale is built for fast scaling of very large databases and read scale out; it does not support auto-pause, so it keeps billing for compute even when the reporting tool is idle. Business Critical with a fixed provisioned size is intended for low-latency, high-availability workloads with constant demand, and provisioning for peak burst wastes money the rest of the day since it never pauses. An elastic pool shares provisioned compute across multiple databases to smooth out combined usage, but it still bills for the pool continuously and does not auto-pause a single idle database.

Reference: Serverless compute tier for Azure SQL Database

Practice Test 8 ›

Study guides for AZ-305