City audit chat requires a record whenever a production deploy finishes. How should the pipeline notify that completion?
Select an answer to reveal the explanation.
Short Explanation
Audit chat shouldn't depend on someone remembering to type 'shipped.' Have the pipeline fire EventBridge or SNS when prod deploy finishes so the record is automatic. Ops gets a timestamped breadcrumb without heroics.
Full Explanation
When city audit chat requires a record whenever a production deploy finishes, the pipeline should emit an EventBridge or SNS notification on successful production deploy completion. Automated completion events create durable, timely audit breadcrumbs without relying on human memory. Municipal auditors expect machine-generated deploy notices tied to pipeline executions.
Asking developers to remember to paste deploy times into a shared spreadsheet is unreliable and non-auditable under stress.
Updating a local laptop sticky note on the release manager's desk is not an organizational audit record.
Disabling pipeline notifications so audit chat stays quiet actively defeats the requirement.
Exam caveat: Use pipeline/deploy success events via SNS or EventBridge to notify humans and systems.
Operational check: Configure CodePipeline/CodeDeploy success notifications to an SNS topic (or EventBridge rule) that posts into audit chat, perform a test production deploy in a controlled window, and verify the message includes execution ID and time. Keep the civic/municipal context in mind: change boards and auditors for city systems expect automatic deploy receipts, not sticky notes. Document the finding in the municipal incident ticket so the next on-call engineer inherits evidence rather than folklore.