You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- content: "Can transactional replication be configured from the Azure portal?"
18
-
choices:
19
-
- content: "No, transactional replication can only be configured through SQL Server Management Studio."
20
-
isCorrect: false
21
-
explanation: "Incorrect. Transactional replication can also be configured by executing Transact-SQL statements on the publisher."
22
-
- content: "Yes, transactional replication can be configured from the Azure portal."
23
-
isCorrect: false
24
-
explanation: "Incorrect. Transactional replication can't be configured from the Azure portal."
25
-
- content: "No, transactional replication can't be configured from the Azure portal."
26
-
isCorrect: true
27
-
explanation: "Correct. Transactional replication can't be configured from the Azure portal."
28
-
- content: "What is the primary use case for the Log Replay Service for Azure SQL Managed Instance?"
29
-
choices:
30
-
- content: "To migrate databases from on-premises SQL Servers or virtual machines to Azure SQL Managed Instance with minimal downtime"
31
-
isCorrect: true
32
-
explanation: "Correct. The primary use case for the Log Replay Service for Azure SQL Managed Instance is to migrate databases from on-premises SQL Servers or virtual machines to Azure SQL Managed Instance with minimal downtime. It's useful in cases when more control is needed, when there exists little tolerance for downtime, or when Azure Data Migration Service can't be used. "
33
-
- content: "To migrate data from other cloud providers to Azure SQL Managed Instance"
34
-
isCorrect: false
35
-
explanation: "Incorrect. The Log Replay Service is designed to enable custom migrations of databases from SQL Servers on-premises, or in a virtual machine, to SQL Managed Instance in Azure. It doesn't support migrations from other cloud providers. "
36
-
- content: "To migrate data from Azure SQL Database to Azure SQL Managed Instance"
37
-
isCorrect: false
38
-
explanation: "Incorrect. The Log Replay Service is designed to enable custom migrations of databases from SQL Servers 2008 through 2019 on-premises, or in a virtual machine, to SQL Managed Instance in the cloud. It doesn't support migrations from Azure SQL Database to Azure SQL Managed Instance. "
39
-
- content: "What is the purpose of using SQL Managed Instance link feature during migration?"
40
-
choices:
41
-
- content: To create an availability group listener on the source and target.
42
-
isCorrect: false
43
-
explanation: Incorrect. This is only required when migrating an availability group.
44
-
- content: To minimize downtime during migration by extending an on-premises database into the cloud.
45
-
isCorrect: true
46
-
explanation: Correct. Using SQL Server Always On availability group (AG) feature can help minimize downtime during migration by extending an on-premises database into the cloud.
47
-
- content: To create a Windows Server Failover Cluster on the source and target.
48
-
isCorrect: false
49
-
explanation: Incorrect. This isn't required when using a distributed AG to migrate a standalone instance.
- content: "Can transactional replication be configured from the Azure portal?"
18
+
choices:
19
+
- content: "No, transactional replication can only be configured through SQL Server Management Studio."
20
+
isCorrect: false
21
+
explanation: "Incorrect. Transactional replication can also be configured by executing Transact-SQL statements on the publisher."
22
+
- content: "Yes, transactional replication can be configured from the Azure portal."
23
+
isCorrect: false
24
+
explanation: "Incorrect. Transactional replication can't be configured from the Azure portal."
25
+
- content: "No, transactional replication can't be configured from the Azure portal."
26
+
isCorrect: true
27
+
explanation: "Correct. Transactional replication can't be configured from the Azure portal."
28
+
- content: "What is the primary use case for the Log Replay Service for Azure SQL Managed Instance?"
29
+
choices:
30
+
- content: "To migrate databases from on-premises SQL Servers or virtual machines to Azure SQL Managed Instance with minimal downtime"
31
+
isCorrect: true
32
+
explanation: "Correct. The primary use case for the Log Replay Service for Azure SQL Managed Instance is to migrate databases from on-premises SQL Servers or virtual machines to Azure SQL Managed Instance with minimal downtime. It's useful in cases when more control is needed, when there exists little tolerance for downtime, or when Azure Data Migration Service can't be used. "
33
+
- content: "To migrate data from other cloud providers to Azure SQL Managed Instance"
34
+
isCorrect: false
35
+
explanation: "Incorrect. The Log Replay Service is designed to enable custom migrations of databases from SQL Servers on-premises, or in a virtual machine, to SQL Managed Instance in Azure. It doesn't support migrations from other cloud providers. "
36
+
- content: "To migrate data from Azure SQL Database to Azure SQL Managed Instance"
37
+
isCorrect: false
38
+
explanation: "Incorrect. The Log Replay Service is designed to enable custom migrations of databases from SQL Servers 2008 through 2019 on-premises, or in a virtual machine, to SQL Managed Instance in the cloud. It doesn't support migrations from Azure SQL Database to Azure SQL Managed Instance. "
39
+
- content: "What is the purpose of using SQL Managed Instance link feature during migration?"
40
+
choices:
41
+
- content: To create an availability group listener on the source and target.
42
+
isCorrect: false
43
+
explanation: Incorrect. This is only required when migrating an availability group.
44
+
- content: To minimize downtime during migration by extending an on-premises database into the cloud.
45
+
isCorrect: true
46
+
explanation: Correct. Using SQL Server Always On availability group (AG) feature can help minimize downtime during migration by extending an on-premises database into the cloud.
47
+
- content: To create a Windows Server Failover Cluster on the source and target.
48
+
isCorrect: false
49
+
explanation: Incorrect. This isn't required when using a distributed AG to migrate a standalone instance.
0 commit comments