A municipal snow-route office used to ship one fixed plow-priority table each November. The replacement system keeps changing those priorities as new storm telemetry arrives. What distinction should the tester recognize?
Select an answer to reveal the explanation.
Short Explanation
A fixed November plow table stays put after one release test. A system that keeps rewriting priorities from new storm telemetry is adaptable AI-based behavior, so monitoring continues after go-live. Adaptability does not retire later checks, and the old table was never adaptive.
Full Explanation
Static conventional software ships one table and stays put. Self-updating AI-based behavior can shift as new data arrives, so testers must keep watching alignment after release. Treating the new system as a one-shot release, or calling the old table adaptive, misses that duty.