What is the recommended approach for removing dead code identified by ADDI before starting the Refactor phase?

Think of it like working hands-on with IBM mainframe systems — the answer here is 'Archive dead code candidates and confirm with business stakeholders they are truly unused before removing them from scope'. Before removing dead code, teams should archive candidates and confirm with business stakeholders that the programs are truly unused, guarding against ADDI missing dynamic call patterns or conditional. On real mainframe exams, this concept comes up repeatedly so make sure you have it locked in.