Basic Concept: This question tests high availability and disaster recovery design for Azure SQL, SQL Server on Azure VMs, and regional failure scenarios.
Why D is Correct: transactional replication to an Azure SQL Managed Instance matches the expected DP-300 administration action. Transactional replication distributes committed changes to subscribers, but it is not the default full-database migration method for Azure SQL Managed Instance when the requirement is minimal effort. The question is not asking for a general Azure capability; it is asking for the feature that produces this result: You need to recommend a disaster recovery solution for an on-premises Microsoft SQL Server database.
Why A is Wrong: database mirroring on an instance of SQL Server on Azure Virtual Machines is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. It handles a different resilience pattern and would not deliver the failover or recovery behavior required here.
Why B is Wrong: availability groups for SQL Server on Azure Virtual Machines is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. It is not wrong technology in general, but it is the wrong HA/DR control for this scenario ' s failure model.
Why C is Wrong: an Azure SQL Managed Instance link is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. It does not meet the failover, restore, quorum, or cross-region continuity target stated in the question, even if it is valid in a different availability design.