A development team runs an Azure SQL Database that is used unpredictably: heavy activity for a few hours during working days, and long idle periods overnight and on weekends. The team wants to minimize compute cost during idle time without manually starting and stopping the database, while still tolerating a short warm-up delay when queries resume. Which compute configuration should you recommend?