AZ-305 Design data storage solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Install DMA, then Assess, then Fix issues, then Migrate and Monitor

  Why this is correct

  This is the correct order because the Data Migration Assistant must be installed first to perform the assessment, then you identify and fix any compatibility issues before migrating the database, and finally monitor the migration.

• ✗

  Assess, then Install DMA, then Fix issues, then Migrate and Monitor

  Why it's wrong here

  This ordering fails because the Data Migration Assistant (DMA) must be installed on the source or a jump host before any assessment can execute; DMA is the engine that inventories the SQL Server, scans object metadata, and detects compatibility and feature-parity issues. Skipping directly to 'Assess' without installing the tool leaves no mechanism to actually run the scan, so the sequence cannot begin. While 'Fix issues' after 'Assess' is logically correct, the installation step must precede assessment, not follow it.

• ✗

  Install DMA, then Migrate and Monitor, then Assess, then Fix issues

  Why it's wrong here

  Jumping straight from tool installation to 'Migrate and Monitor' bypasses the assessment phase, which is essential to surface breaking changes, deprecated features, and object-level incompatibilities that DMA would flag before any data movement. Attempting a migration without remediating those findings can cause schema-transfer failures, data loss, or invalid target objects, and monitoring a blind migration gives no opportunity to correct issues before they impact the cutover. Additionally, running 'Assess' and 'Fix issues' after the migration is operationally contradictory because the source has already been moved and any needed fixes would have to be applied to the live target under pressure.

• ✗

  Fix issues, then Install DMA, then Assess, then Migrate and Monitor

  Why it's wrong here

  This sequence starts with 'Fix issues' before an assessment has been performed, which is logically impossible because no inventory of blockers has been generated to tell you what to fix. DMA's assessment is the sanctioned way to enumerate compatibility and feature-parity problems; attempting fixes without that baseline is guesswork and could unnecessarily alter the source database. Moreover, installing DMA after the fix step means you would still need to re-run the assessment to confirm your changes were sufficient, making the entire order redundant and unsafe.

Go deeper

Related to this question