What is the expected outcome of applying an upgrade directly to the existing MST build without rebuilding?

• A. The upgrade will fail
• B. The upgrade can be applied directly to the existing MST build and MST remains intact
• C. The upgrade will delete MST data
• D. The upgrade cannot be performed

Answer: (B)

In-place upgrades are designed to update software without starting from scratch. When you apply the upgrade directly to the existing MST build, the new code and components are brought in, but the stored data, configurations, and identifiers that MST relies on are preserved. If the upgrade path is validated for this build, it can run over the current installation and MST remains intact because only the executables and libraries change, not the data that MST uses. This is why the expected outcome is that the upgrade can be applied directly and MST stays intact. If a rebuild were required, you’d expect potential data loss or re-creation of the environment, which isn’t the case here. Always ensure compatibility and back up beforehand, but the direct upgrade path means a smooth in-place update with preserved MST data.