What is the benefit of using the UPGANA.XML file from a previous SUM run?

Question

Options

• ATo make the progress information within SUM UI more accurate
• BTo skip selected phases during the SUM run
• CTo repeat specific phases during the SUM run
• DTo auto-fill specific fields on selected screens on the SUM UI

• A
  88% (58)
• B
  8% (5)
• C
  2% (1)
• D
  3% (2)

Explanation

Using the UPGANA.XML file (short for UPGrade ANAlysis) from a prior SUM run gives SUM a detailed picture of the total workload before execution begins. Because the analysis phase has already been completed and stored, SUM can accurately calculate how much work remains at any given moment, resulting in more precise progress bars and time estimates in the UI - this is why A is correct.

Why the distractors are wrong:

• B (skip phases): UPGANA.XML contains analysis output, not execution control flags; skipping phases is not a function it provides.
• C (repeat phases): Similarly, re-running or looping phases is controlled by SUM's own restart/retry mechanisms, not by this file.
• D (auto-fill fields): Pre-populating UI fields is handled by SUM parameter files (like PARAMS.INI), not the upgrade analysis XML.

Memory tip: Think of UPGANA as a "road map" generated from a previous trip - SUM already knows every turn ahead, so the ETA (progress indicator) shown on the dashboard is far more reliable than if it were navigating blind.

No community discussion yet for this question.