Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases that have varying and unpredictable usage demands. The databases in an elastic pool are on a single server and share a set number of resources at a set price.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview Basic Concept: This question tests Azure SQL sizing and purchasing choices, where compute model, scaling behavior, licensing benefits, and cost pattern must be evaluated together.
Why A is Correct: two Azure SQL Databases in an elastic pool matches the expected DP-300 administration action. 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. The question is not asking for a general Azure capability; it is asking for the feature that produces this result: You need to dynamically scale resources consumption based on workloads.
Why B is Wrong: two databases hosted in SQL Server on an Azure virtual machine 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 would solve a neighboring problem, but not the deployment, sizing, or migration requirement in this item.
Why C is Wrong: two databases in an Azure SQL Managed instance 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.
Why D is Wrong: two single Azure SQL databases 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 applies to a different Azure data-platform design than the one the question is testing.