An airline's prebuilt disruption copilot already rebooks routine delays. The only gap is a local crew-rest message the product can accept as added content. A team wants a full custom build of the same copilot. What should the architect choose?
Select an answer to reveal the explanation.
Short Explanation
You do not commission a second aircraft to hang one new placard in the cabin. You extend the prebuilt disruption copilot with the crew-rest message. A full custom build is a costly copy of a copilot the airline already flies.
Full Explanation
The prebuilt disruption copilot already rebooks routine delays, and the product can take the local crew-rest message as added content, so extending it covers the gap. A full custom build repeats that rebooking flow at a higher cost and does not buy a capability the extension lacks. Buying a second disruption product puts two tools on the same delays and still is not the small content change the crew-rest message actually is. Retiring the prebuilt copilot until a custom model drafts crew-rest text throws away a working rebooking flow for a generator that has no disruption product under it. Exam caveat: the crew-rest message has to stay aligned with the airline's operations manual, and an extension can still be wrong if the text is outdated. Operational check: run a routine delay that should include the crew-rest message and confirm the prebuilt copilot rebooks as before and includes that message, with no second copilot in the path. Compare the estimate for a full custom build with the cost of adding that one message, and keep the custom project closed unless the prebuilt copilot cannot hold the text.