After a test-environment deploy of a permit-write API, the pipeline should prove one critical path still works without leaving junk data. What should run next?
Select an answer to reveal the explanation.
Short Explanation
Smoke the kitchen after remodel—one burner on, then wipe the counters. A canary write/read with cleanup proves the path without littering the test table. Waiting for citizens or laptop-only clicks is too late or too tribal.
Full Explanation
Post-deploy canary checks in lower environments automate validation of a critical application path after infrastructure and code are live. A scripted write/read with cleanup confirms end-to-end behavior without polluting shared test data. Relying only on stack success, production reports, or undocumented manual clicks weakens the automated testing gate.