A city permitting office relocates its long-lived JVM monolith onto OCI Compute instances with the same nightly patch cycle and shared in-memory session store. Which change would most clearly move the workload toward a cloud-native design?
Select an answer to reveal the explanation.
Short Explanation
Think of the platform like a fleet of interchangeable city buses: you design for routes and capacity, not for keeping one particular bus forever. Lift-and-shift keeps the same nursed monolith on IaaS. Cloud-native means elastic units, declared desired state, and replaceable infrastructure.
Full Explanation
Relocating an unchanged JVM stack onto OCI Compute is still a traditional deploy pattern: hosts are tended, sessions live in process memory, and releases remain large. Cloud-native design treats the platform as elastic by shipping small independent units, expressing desired state for the runtime to reconcile, and replacing failed or outdated infrastructure instead of patching it in place. Networking or backup improvements alone do not create that posture.