Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests 2026 – Your All-in-One Guide to Exam Success!

Recommending an elastic pool that contains 20 Azure SQL databases is the ideal choice for several reasons. First, elastic pools are designed to manage a collection of Azure SQL databases that share resources, which is particularly advantageous in this scenario where there are 20 databases. By using an elastic pool, you can efficiently share resources such as DTUs or vCores across these databases, allowing for dynamic scaling based on the actual load and performance needs. This means that when one database experiences higher traffic or resource consumption, it can draw from the pool without requiring manual intervention or over-provisioning.

The 99.99% SLA requirement is also met with Azure SQL Database elastic pools, providing strong uptime and reliability. Since the solution can handle varying workloads across the 20 databases, it also optimizes cost management—only what is needed is provisioned, reducing waste.

Moreover, the Azure SQL Database platform is fully managed, ensuring automatic updates, patching, and backups, which allows you to focus more on application development rather than database maintenance.

In contrast, the other options like running SQL Server on a virtual machine do not provide the same level of dynamic scaling and management efficiency inherent in Azure SQL Database elastic pools. They generally involve more overhead and require manual