E_S4CON_2505 · Question #15
Which step can be optimized when you provide the MIGRATE_DT_DUR.XML file to SUM?
The correct answer is B. Downtime migration. Providing MIGRATE_DT_DUR.XML to SUM (Software Update Manager) gives it pre-measured duration data from a prior migration run, allowing it to optimize the Downtime Migration step (B) by skipping the re-estimation phase and using the cached timings directly - reducing overall…
Question
Which step can be optimized when you provide the MIGRATE_DT_DUR.XML file to SUM?
Options
- ADowntime conversion
- BDowntime migration
- CShadow on target creation
- DSilent data migration (SDM)
How the community answered
(23 responses)- A9% (2)
- B74% (17)
- C4% (1)
- D13% (3)
Explanation
Providing MIGRATE_DT_DUR.XML to SUM (Software Update Manager) gives it pre-measured duration data from a prior migration run, allowing it to optimize the Downtime Migration step (B) by skipping the re-estimation phase and using the cached timings directly - reducing overall downtime.
Why the distractors are wrong:
- A (Downtime Conversion) involves data type/format conversion during downtime, which is a separate process not influenced by this duration file.
- C (Shadow on Target Creation) is an uptime phase where the shadow system is built; duration data from a prior migration run has no role in creating it.
- D (Silent Data Migration) runs in the background during uptime and operates independently of downtime duration estimates.
Memory tip: Decode the filename - MIGRATE_DT_DUR.XML = Migrate + DownTime + Duration. The name literally spells out what it optimizes: the downtime migration duration.
Topics
Community Discussion
No community discussion yet for this question.