Basic Concept: This question tests Azure monitoring and performance management, including which metric, log destination, or alerting behavior fits the operational requirement.
Why B is Correct: the serverless compute tier is correct because it is the feature whose normal purpose matches the stated requirement. The serverless tier automatically scales compute and can pause during inactive periods, making it suitable for intermittent workloads with bursts and idle windows. The scenario wording points to that specific behavior: You need to deploy an Azure SQL database.
Why A is Wrong: Business Critical provides low-latency local SSD storage and high availability for demanding workloads, but it is usually more expensive than necessary for bursty idle workloads. That design keeps capacity available for a different kind of workload and does not match the cost behavior expected from an idle-and-burst database pattern.
Why C is Wrong: Elastic pools let multiple Azure SQL databases share a fixed pool of resources, which is cost-effective when individual database usage is variable and unpredictable. It would solve a neighboring problem, but not the deployment, sizing, or migration requirement in this item.
Why D is Wrong: the General Purpose service tier is an Azure data-platform feature, but it must match the workload model, service tier, migration path, or deployment constraint described in the scenario. It mismatches the target platform, migration method, compute tier, or deployment model described in the scenario, so it would not satisfy the workload as stated.