Exam DP-300 topic 3 question 37 discussion

You can enable auto tuning by Azure Portal and T-SQL. To enable automatic tuning on a single database via T-SQL, connect to the database and execute the following query: ALTER DATABASE current SET AUTOMATIC_TUNING = AUTO | INHERIT | CUSTOM So, option C is wrong.Answer is B:Azure Portal configuration auto tuning. Ref: https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql#t-sql

Checking the Azure portal settings for SQL MI and its databases, I did not find a section for automatic tuning (like Azure SQL DB has). Hence, answer is C: Use the T-SQL

For Azure SQL Managed Instance, the supported option FORCE_LAST_GOOD_PLAN can only be configured through T-SQL. The Azure portal based configuration and automatic index tuning options described in this article do not apply to Azure SQL Managed Instance. https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql-mi

C is the correct answer, force_last_good_plan for SQL managed instance. For Azure SQL Managed Instance, the supported option FORCE_LAST_GOOD_PLAN can only be configured through T-SQL. The Azure portal based configuration and automatic index tuning options described in this article do not apply to Azure SQL Managed Instance. https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql#enable-automatic-tuning-on-an-individual-database

https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-overview?view=azuresql "Enable automatic tuning Azure SQL Database: Enable automatic tuning in the Azure portal or by using the ALTER DATABASE T-SQL statement. Azure SQL Managed Instance: Enable automatic tuning by using the ALTER DATABASE T-SQL statement." So FORCE_LAST_GOOD_PLAN is the correct answer, as it is provided by MS itself.

https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-overview?view=azuresql#enable-automatic-tuning - This states that enabling via portal is only available for Azure DB not MI

https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql For Azure SQL Managed Instance, the supported option FORCE_LAST_GOOD_PLAN can only be configured through T-SQL. The Azure portal based configuration and automatic index tuning options described in this article do not apply to Azure SQL Managed Instance.

C is missing the create_index and drop_index options, so answer is B, use the Azure Portal to enable AT although it could be done using T-SQL as well.

The correct answer is B To implement automatic tuning for the databases of an Azure SQL managed instance, you can configure automatic tuning from the Azure portal. In the Azure portal, navigate to your managed instance and select “Automatic tuning” from the menu. From there, you can enable or disable automatic tuning options such as “Force plan” and “Create index”. Therefore, the correct answer is B. From the Azure portal, configure automatic tuning. Option C is also incorrect because enabling the FORCE_LAST_GOOD_PLAN option is not related to automatic tuning. FORCE_LAST_GOOD_PLAN is a query hint that forces a query to use the last known good query plan in the plan cache instead of generating a new one.

https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql - read first highlighted area

For Azure SQL Managed Instance, the supported option FORCE_LAST_GOOD_PLAN can only be configured through T-SQL. The Azure portal based configuration and automatic index tuning options described in this article do not apply to Azure SQL Managed Instance. Ref: https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql

Correct, managed instance is via alter database: <automatic_tuning_option> ::= { AUTOMATIC_TUNING ( FORCE_LAST_GOOD_PLAN = { DEFAULT | ON | OFF } ) } azure sql database can also be done via the portal