Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/migrate-to-database-from-sql-server#method-1- migration-with-downtime-during-the-migration Basic Concept: This question tests choosing the correct Azure migration approach by matching the source platform, target service, downtime tolerance, and administrative effort.
Why C is Correct: 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 scenario asks for: You need to migrate an on-premises Microsoft SQL Server database to Azure SQL Database. That makes Configure transactional replication. the option that satisfies the required Azure SQL layer and operational outcome.
Why A is Wrong: Log shipping is a SQL Server HA/DR technique that copies and restores log backups to a secondary database; it is more manual and operationally heavier for Azure SQL Managed Instance migration than LRS. 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.
Why B is Wrong: Always On availability groups are SQL Server/SQL Managed Instance HA technology, not the Azure SQL Database PaaS failover abstraction used for database groups. It handles a different resilience pattern and would not deliver the failover or recovery behavior required here.
Why D is Wrong: Import a BACPAC. 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.