A water-department product team ships a billing microservice but still pages a separate operations group whenever the service misbehaves at 2 a.m. Which cloud-native principle are they missing?
Select an answer to reveal the explanation.
Short Explanation
DevOps culture is like a neighborhood watch where the builders also answer the night call—not a handoff over a fence. Shared ownership and tight feedback loops are the principle. Pipeline SKUs and quarterly boards are not the point of this pillar.
Full Explanation
Cloud-native delivery assumes developers own shipping and runtime behavior, closing the loop between code and production signals. Splitting “build” from “2 a.m. ownership” recreates wall-of-confusion handoffs. The principle is cultural and operational; it is not an OCI DevOps pipeline design question or a multi-region DR architecture quiz.