A county Migration Hub portfolio assessment is about to lock wave one for courts and assessor systems, but Application Discovery Service just reported undocumented departmental servers that never appeared in the CMDB. What should the architects do before finalizing the wave?
Select an answer to reveal the explanation.
Short Explanation
Think of packing for a move and finding three mystery boxes in the attic the day before the truck leaves. Discovery just surfaced stealth IT the CMDB never knew about, so fold those assets into the portfolio and re-check dependencies before you lock wave one.
Full Explanation
Professional migration selection depends on a complete portfolio. Application Discovery and related discovery tools commonly reveal undocumented servers that CMDB inventories miss; those assets must enter the Migration Hub portfolio so dependencies, owners, and 7R strategies are assessed before waves lock. Freezing an incomplete inventory, blindly stuffing finds into wave one, or waiting until after cutover all increase failed cutovers and unplanned outages.