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
description: "This unit introduces the module on choosing a tool to migrate data to an Azure Database for MySQL flexible server. It covers migration phases and considerations, tool options, and migration approaches."
description: "This unit introduces the module on choosing a tool to migrate data to an Azure Database for MySQL flexible server. It covers migration phases and considerations, tool options, and migration approaches."
description: "This unit covers migration tool options for Azure Database for MySQL - Flexible Server. It addresses mysqldump, MySQL Workbench, MySQL binlog, mydumper, myloader, Azure Migrate, Azure Database Migration Service (DMS), and the Azure Database for MySQL Import CLI."
description: "This unit covers migration tool options for Azure Database for MySQL - Flexible Server. It addresses mysqldump, MySQL Workbench, MySQL binlog, mydumper, myloader, Azure Migrate, Azure Database Migration Service (DMS), and the Azure Database for MySQL Import CLI."
description: "This unit is the knowledge check for the module migrating data to Azure Database for MySQL - Flexible Server. It covered migration phases and considerations, tool options, and migration approaches."
- content: "An in-place major version migration that keeps the database online."
33
-
isCorrect: false
34
-
explanation: "A database has to restart to update major versions. An online migration refers to the entire application staying online."
35
-
- content: "A server-to-server data migration that keeps the application online."
36
-
isCorrect: true
37
-
explanation: "Correct, an online migration refers to application downtime."
38
-
- content: "A server-to-server migration using an online connection."
39
-
isCorrect: false
40
-
explanation: "Transferring data with an online connection is part of an online migration, but not the full story. Live connections on write-frozen databases can also be used for bulk transfer for an offline migration."
41
-
- content: "You’re migrating a MySQL database running on a VM to an Azure Database for MySQL flexible server. The application can tolerate about an hour, but not several hours, of downtime. A full backup (several years of data) takes about 4 hours to restore. What’s the best option?"
42
-
choices:
43
-
- content: "An online migration."
44
-
isCorrect: false
45
-
explanation: "While an online migration would remove the downtime, its extra complexity when the application can tolerate about an hour of downtime."
46
-
- content: "An offline migration using a full snapshot."
47
-
isCorrect: false
48
-
explanation: "A full snapshot would take about 4 hours to restore. The application would have to be online during this process (at least), which exceeds the one hour downtime target."
49
-
- content: "An offline migration using a full snapshot and an incremental snapshot."
50
-
isCorrect: true
51
-
explanation: "This is the best choice. The four hour transfer can occur first. Then, the application can go down to capture & migrate the smaller increment, to fit within the hour of downtime."
52
-
- content: "You want to migrate your on-premises MySQL database to Azure because it exhausts processing and storage resources regularly. Near-zero downtime is preferable. Which of these approaches should you consider?"
53
-
choices:
54
-
- content: "Restore the database from a snapshot and use the binary log to synchronize changes that occurred since the snapshot was taken."
55
-
isCorrect: false
56
-
explanation: "While this is a way to eliminate downtime, it's manual and error-prone compared to automated approaches like Azure Database Migration Service."
57
-
- content: "Use mydumper and myloader to create and restore data."
58
-
isCorrect: false
59
-
explanation: "Even though these tools are fast, they'll still require downtime to migrate data once the application is frozen."
60
-
- content: "Use Azure Database Migration Service to automate migration and minimize downtime."
61
-
isCorrect: true
62
-
explanation: "Azure DMS automates the migration process, and can perform an online migration, or a near-zero downtime offline migration."
63
-
- content: "You want to test application changes against realistic data. Which option should you pick?"
64
-
choices:
65
-
- content: "Restore database backups into development environments."
66
-
isCorrect: false
67
-
explanation: "Unless necessary, this poses a security risk as it places full customer data into nonproduction environments."
68
-
- content: "Use a tool like mysqldump to create controlled test scenarios."
69
-
isCorrect: true
70
-
explanation: "A test scenario should contain PERSONAL DATA-safe customer data, if any customer data at all. The mysqldump allows you to build selective test scenarios."
71
-
- content: "Use Azure Database for MySQL Import CLI to create test data."
72
-
isCorrect: false
73
-
explanation: "This isn't one of the Import CLI's features."
74
-
- content: "You want to migrate a high-availability flexible server from one region to another. Some downtime is acceptable. Which is the simplest solution?"
75
-
choices:
76
-
- content: "Use mydumper and myloader to migrate two parallel instances, then enable replication."
77
-
isCorrect: false
78
-
explanation: "While highly available databases do have two instances, the high availability comes from other mechanisms such as managed failover (not just replication)."
79
-
- content: "Use MySQL Workbench to set up two target databases and perform a migration, then enable replication."
80
-
isCorrect: false
81
-
explanation: "While highly available databases do have two instances, the high availability comes from other mechanisms such as managed failover (not just replication)."
82
-
- content: "Use Percona XtraBackup and Azure Database for MySQL Import CLI to create the target server, and then enable HA."
83
-
isCorrect: true
84
-
explanation: "This is a simple way to migrate the data, and ensure managed high-availability in the flexible server."
description: "This unit is the knowledge check for the module migrating data to Azure Database for MySQL - Flexible Server. It covered migration phases and considerations, tool options, and migration approaches."
- content: "An in-place major version migration that keeps the database online."
33
+
isCorrect: false
34
+
explanation: "A database has to restart to update major versions. An online migration refers to the entire application staying online."
35
+
- content: "A server-to-server data migration that keeps the application online."
36
+
isCorrect: true
37
+
explanation: "Correct, an online migration refers to application downtime."
38
+
- content: "A server-to-server migration using an online connection."
39
+
isCorrect: false
40
+
explanation: "Transferring data with an online connection is part of an online migration, but not the full story. Live connections on write-frozen databases can also be used for bulk transfer for an offline migration."
41
+
- content: "You’re migrating a MySQL database running on a VM to an Azure Database for MySQL flexible server. The application can tolerate about an hour, but not several hours, of downtime. A full backup (several years of data) takes about 4 hours to restore. What’s the best option?"
42
+
choices:
43
+
- content: "An online migration."
44
+
isCorrect: false
45
+
explanation: "While an online migration would remove the downtime, its extra complexity when the application can tolerate about an hour of downtime."
46
+
- content: "An offline migration using a full snapshot."
47
+
isCorrect: false
48
+
explanation: "A full snapshot would take about 4 hours to restore. The application would have to be online during this process (at least), which exceeds the one hour downtime target."
49
+
- content: "An offline migration using a full snapshot and an incremental snapshot."
50
+
isCorrect: true
51
+
explanation: "This is the best choice. The four hour transfer can occur first. Then, the application can go down to capture & migrate the smaller increment, to fit within the hour of downtime."
52
+
- content: "You want to migrate your on-premises MySQL database to Azure because it exhausts processing and storage resources regularly. Near-zero downtime is preferable. Which of these approaches should you consider?"
53
+
choices:
54
+
- content: "Restore the database from a snapshot and use the binary log to synchronize changes that occurred since the snapshot was taken."
55
+
isCorrect: false
56
+
explanation: "While this is a way to eliminate downtime, it's manual and error-prone compared to automated approaches like Azure Database Migration Service."
57
+
- content: "Use mydumper and myloader to create and restore data."
58
+
isCorrect: false
59
+
explanation: "Even though these tools are fast, they'll still require downtime to migrate data once the application is frozen."
60
+
- content: "Use Azure Database Migration Service to automate migration and minimize downtime."
61
+
isCorrect: true
62
+
explanation: "Azure DMS automates the migration process, and can perform an online migration, or a near-zero downtime offline migration."
63
+
- content: "You want to test application changes against realistic data. Which option should you pick?"
64
+
choices:
65
+
- content: "Restore database backups into development environments."
66
+
isCorrect: false
67
+
explanation: "Unless necessary, this poses a security risk as it places full customer data into nonproduction environments."
68
+
- content: "Use a tool like mysqldump to create controlled test scenarios."
69
+
isCorrect: true
70
+
explanation: "A test scenario should contain PERSONAL DATA-safe customer data, if any customer data at all. The mysqldump allows you to build selective test scenarios."
71
+
- content: "Use Azure Database for MySQL Import CLI to create test data."
72
+
isCorrect: false
73
+
explanation: "This isn't one of the Import CLI's features."
74
+
- content: "You want to migrate a high-availability flexible server from one region to another. Some downtime is acceptable. Which is the simplest solution?"
75
+
choices:
76
+
- content: "Use mydumper and myloader to migrate two parallel instances, then enable replication."
77
+
isCorrect: false
78
+
explanation: "While highly available databases do have two instances, the high availability comes from other mechanisms such as managed failover (not just replication)."
79
+
- content: "Use MySQL Workbench to set up two target databases and perform a migration, then enable replication."
80
+
isCorrect: false
81
+
explanation: "While highly available databases do have two instances, the high availability comes from other mechanisms such as managed failover (not just replication)."
82
+
- content: "Use Percona XtraBackup and Azure Database for MySQL Import CLI to create the target server, and then enable HA."
83
+
isCorrect: true
84
+
explanation: "This is a simple way to migrate the data, and ensure managed high-availability in the flexible server."
0 commit comments