After each staging deploy of a citizen records API, the team wants a fast signal that the environment is basically healthy. What should they automate?
Select an answer to reveal the explanation.
Short Explanation
After you land the plane, check the doors still open. A tiny smoke script—health plus one authenticated read—tells you staging is alive before QA piles on. Waiting for production complaints is not a smoke test.
Full Explanation
Automated smoke tests against deployed development or staging environments catch broken routes, auth miswiring, and bad configuration immediately after deploy. Unit tests do not replace that live check. Citizen-reported production failures and infrequent manual clicks are too late for municipal release quality.