Exam AZ-301 topic 5 question 10 discussion

Shouldn't this B and D? Both SQL Server on Azure VM and SQL Managed Instance can support cross-database queries wherein server.dbName.tableName is used. Stretch Database is for migrating cold data transparently and securely to the Azure cloud.

A is wrong, Stretch Database is a feature of SQL Server where data can be split between on-premises storage and cloud storage. With Stretch Database, cold, historical data is kept in the cloud and active data is kept on-premises for maximum performance. The requirement is to migrate the application instance to Azure. A is partial migrate which doesn't fulfill the requiremnt.

B and D make sense.

B. SQL Server in an Azure virtual machine D. SQL Managed Instance

B and D are correct answer.

A and D are correct

Okay now I am confident that "Linked Servers" is the feature to use here, because of this statement; "App consumes data from __multiple__ DBs and code references tables using a combination of the __server, database, and table name__". So Linked Servers are already getting used. A query would look like this SELECT col1, col2 FROM [linkedservername].[databasename].[schemaname].[tablename] So the answer is definitly B) and D) as this are the only options supporting this feature!

This question really drives me mad. Another possibility is that Microsoft expects a solution based on the "Linked Servers" feature. This would allow a client to talk to a single endpoint which then performs distributed queries. If so, then B & D would be the correct answer, as only "SQL Server Database Engine" and "Azure SQL MI" support this feature... https://docs.microsoft.com/en-us/sql/relational-databases/linked-servers/linked-servers-database-engine?view=sql-server-ver15#linked-server-details

I too think that A) and D) are correct, because: A. SQL Server Stretch Database: Can be used to stretch _warm_ and cold data... and further a quote: "Doesn't require changes to queries or applications [...] the location of the data is transparent to the application". https://docs.microsoft.com/en-us/sql/sql-server/stretch-database/stretch-database?view=sql-server-ver15 D. SQL Managed Instance Supports custom DNS, which would allow to add a name the fits the references in the code... https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/custom-dns-configure

A & D is correct. https://azure.microsoft.com/en-us/services/sql-server-stretch-database/#overview https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview

A & D are correct answers

Too many limitations for the Stretched Database DML operations You can't UPDATE or DELETE rows that have been migrated, or rows that are eligible for migration, in a Stretch-enabled table or in a view that includes Stretch-enabled tables. You can't INSERT rows into a Stretch-enabled table on a linked server. Indexes You can't create an index for a view that includes Stretch-enabled tables. Filters on SQL Server indexes are not propagated to the remote table.

Considering the question says: 1. "migrate the app (not DBs) instance to Azure" 2. "combination of the server, database, and table name" and Except if Managed Instance can use the same server name, I think the correct answers would be A and B

Agree. With B & D

Answer is B&D

https://docs.microsoft.com/en-us/sql/sql-server/stretch-database/stretch-database?view=sql-server-ver15 "Doesn't require changes to queries or applications Access your SQL Server data seamlessly regardless of whether it's on-premises or stretched to the cloud. You set the policy that determines where data is stored, and SQL Server handles the data movement in the background. The entire table is always online and queryable. And, Stretch Database doesn't require any changes to existing queries or applications - the location of the data is completely transparent to the application." So I think "A". Stretch Database is correct

I think A, B and D are fulfilled the requirement. refer to : https://docs.microsoft.com/en-us/azure/sql-database/sql-database-features