Microsoft Azure Solutions Architect Expert AZ-305 Practice Question

Azure SQL Managed Instance offers near-full engine compatibility with on-premises SQL Server, including built-in SQL Server Agent, CLR integration (with some limitations), and native cross-database querying. Because it is deployed inside an Azure Virtual Network, it provides private connectivity. Using Azure Database Migration Service in online mode keeps the source database operational while continuously replicating changes, so the final cut-over can be completed within the required two-hour window.

Exporting a 10-TB BACPAC and importing it into Azure SQL Database Hyperscale is an asynchronous process that leaves the source database online, but the export and large-scale import typically take many hours and the target platform lacks SQL Server Agent, CLR, and cross-database capabilities, violating multiple requirements. Restoring a 10-TB backup to SQL Server on an Azure VM generally takes several hours-longer than the downtime limit-and does not provide a managed PaaS environment. Transactional replication to Azure SQL Database fails to migrate CLR objects, lacks full SQL Server Agent parity, and still does not support cross-database queries, making it unsuitable.