A court-scheduling service takes several minutes of JVM warm-up before accepting traffic and ignores termination signals, dropping in-flight bookings when instances are replaced. Which disposability improvement should the team prioritize?
Select an answer to reveal the explanation.
Short Explanation
Disposability is like a fire crew that can suit up in seconds and hand off the hose cleanly when relieved. Fast startup and graceful shutdown make scale-out and self-heal real. Long warm-ups and ignored termination signals fight the platform.
Full Explanation
Scale-out and self-healing assume new processes become useful quickly and dying processes finish or refuse work instead of dropping it. Multi-minute warm-ups and ignored signals undermine those platform behaviors. Stretching warm-up, hard-crashing without drain, or refusing restarts all work against disposability. Probe field memorization is not required for this fundamentals item.