A parks-and-recreation team wants the platform to keep three healthy replicas of its reservation API without an operator running start and stop checklists. Which cloud-native pillar describes that approach?
Select an answer to reveal the explanation.
Short Explanation
Declarative control is like telling a thermostat the temperature you want, not flipping the heater switch yourself every hour. You publish desired state; the platform converges. Imperative checklists and SSH snowflakes fight that model.
Full Explanation
Declarative APIs encode intent such as replica count and health expectations, then controllers reconcile actual state toward that intent. Imperative start/stop lists, static single-host sizing, and post-boot SSH edits leave humans as the control loop and invite drift. The exam concept is the desired-state pillar, not a specific YAML field or CLI flag.