A city open-data portal team wants high-impact configuration changes to feel routine instead of heroic overnight projects. Which approach best matches the cloud-native goal of frequent, predictable change?
Select an answer to reveal the explanation.
Short Explanation
Automation is the boring highway from commit to running revision—the goal is frequent, predictable, low-toil change. Manual tribal checklists and giant weekend batches make high-impact work dramatic again. The principle is the goal, not picking a pipeline SKU.
Full Explanation
Cloud-native shops invest in automation so deploying a revision is repeatable and low drama. That enables frequent change without proportional human toil. Ad-hoc checklists, large batched freezes, and SSH-only senior rituals work against predictability. OCI DevOps product wiring is out of scope for this fundamentals item.