問題文
A company must modernize a critical legacy system without a risky big-bang rewrite. Which phased, API-led approach fits?
選択肢
- Rewrite the entire legacy system in one big-bang release before any consumer may use its data, accepting the maximum risk and delay as the only path to modernization.
- Front the legacy system with a System API and move consumers onto it, then evolve or replace the legacy behind that stable interface over time.
- Legacy modernization cannot be phased and must always be done all at once, and the company has to accept one high-risk cutover date for the system.
- Give every consumer the legacy system's raw internal access so they depend on its internals directly, which is what makes a later replacement safe and low-risk.