DMA does not support database migrations to Azure SQL Managed Instance. Recommendation is to use the Azure SQL migration extension for Azure Data Studio, which supports both online and offline database migrations to Azure SQL Managed Instance, but here we don't have the option "Azure SQL migration extension for Azure Data Studio".
https://learn.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-ver16#capabilities Regarding log shipping to Managed Instance is not possible; it only supports the restore of full backups.
https://dba.stackexchange.com/questions/232332/is-it-possible-to-log-ship-from-on-premise-sql- server-to-azure-sql-managed-insta
https://docs.microsoft.com/en-us/azure/azure-sql/migration-guides/managed-instance/sql-server- to-managed-instance-guide

Explanation:
Box 1: no extra time
Auto Pause is not checked in the exhibit.
Note: If Auto Pause is checked the correct answer is: up to one minute
Box 2: intermittent and unpredictable
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview

https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale?view=azuresql#compare-resource-limits

Append Mode: Only new rows appended in the result table since the last trigger are written to external storage. This is applicable only for the queries where existing rows in the Result Table are not expected to change.
Complete Mode: The entire updated result table is written to external storage. It is up to the storage connector to decide how to handle the writing of the entire table.
Update Mode: Only the rows that were updated in the result table since the last trigger are written to external storage. This is different from Complete Mode in that Update Mode outputs only the rows that have changed since the last trigger. If the query doesn't contain aggregations, it is equivalent to Append mode.
Reference:
https://docs.databricks.com/getting-started/spark/streaming.html

Explanation:
Box 1: SET QUERY_STORE = ON (OPERATION MODE = READ_WRITE);
As a pre-requisite, Query Store must be turned on.
Box 2: SET AUTOMATIC_TUNING (FORCE_LAST_GOOD_PLAN = ON)
To configure individual automatic tuning options via T-SQL, connect to the database and execute the query such as this one:
ALTER DATABASE current SET AUTOMATIC_TUNING (FORCE_LAST_GOOD_PLAN = ON) Setting the individual tuning option to ON will override any setting that database inherited and enable the tuning option.
Setting it to OFF will also override any setting that database inherited and disable the tuning option.
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/automatic-tuning/automatic-tuning
https://docs.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable