HOTSPOT You have two on-premises Microsoft SQL Server 2017 instances that host an Always On availability group named AG1. AG1 contains a single database named DB1. You have an Azure subscription that contains a virtual machine named VM1VM1 runs Linux and contains a SQL Server 2019 instance. You need to migrate DB1 to VMI. The solution must minimize downtime on DBI. What should you do? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. 
Not quite log shipping here. The key is "minimize downtime" and distributed AG nails that, since it lets you sync across the AG boundary before cutover. You need to prep by creating an AG on VM1 first-otherwise you can't do the distributed setup. Saw a similar question in practice exams, trap is picking just log shipping because it's easier but doesn't hit the minimal downtime requirement.
Create an Always On availability group on VM1 first, then use a distributed availability group for the migration. Distributed AGs let you sync between two AGs even across different OS versions, which should keep downtime really low for DB1. Pretty sure that's how it's done in hybrid migrations.
Can you even use distributed AGs between SQL Server 2017 and 2019 when one is Linux? I know distributed AG is the usual choice to minimize downtime, but I'm not totally sure all features are supported cross-version and OS. Would log shipping be the backup here if that's an issue?
