Basic Concept: This question tests high availability and disaster recovery design for Azure SQL, SQL Server on Azure VMs, and regional failure scenarios.
Why C is Correct: Active geo-replication creates readable secondary databases, but failover groups add the managed listener and automatic failover abstraction needed for application continuity at scale. This fits the case because the requested outcome is: You need to ensure that you have a secondary replica of SQLI in the same region. The selected feature addresses that outcome directly rather than relying on a workaround.
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: Auto-failover groups provide managed geo-replication and listener-based failover for Azure SQL Database or Managed Instance, including automatic failover policies for regional outages. It handles a different resilience pattern and would not deliver the failover or recovery behavior required here.
Why D is Wrong: Microsoft SQL Server failover clusters 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.