A library consortium containerizes its catalog app but still requires a stop-the-world release whenever any module changes, and operators cannot see why requests fail. What outcomes should the cloud-native pillars primarily unlock?
Select an answer to reveal the explanation.
Short Explanation
The pillars are not trophies for “we used a container”—they are tools so one change does not freeze the whole city hall, a failed unit can be swapped, and operators can see and steer. Loose coupling, resilience, manageability, and observability are the outcomes that matter.
Full Explanation
Techniques such as containers and declarative control exist to produce loosely coupled, resilient, manageable, and observable systems. Container packaging without those outcomes is cargo-cult. Billing trivia, mandating a mesh, or forcing multi-region topologies for every service miss the purpose of the fundamentals domain.