Ops wants SNS notices when account-level Lambda concurrency nears quota and when a production deploy finishes. What should they implement?
Select an answer to reveal the explanation.
Short Explanation
Wire alarms and deploy notifications to SNS when concurrency nears quota or prod finishes shipping. Quiet spreadsheets do not page anyone at 2 a.m.
Full Explanation
Ops wanting SNS notices when account-level Lambda concurrency nears quota and when a production deploy finishes should implement notification alerts—CloudWatch alarms on concurrency/quota-related metrics and CodePipeline or CodeDeploy notifications—publishing to Amazon SNS. SNS then fans out to email, ChatOps, or paging so municipal engineers hear both capacity risk and deploy completion without polling consoles.
Manual spreadsheet checks once a quarter cannot warn about concurrency exhaustion in time.
Amazon Macie sensitive-data findings are not a deploy-complete signal.
S3 static website hosting events do not replace concurrency and deploy alerts.
Exam caveat: Wire alarms and pipeline notifications to SNS for operational awareness; know which AWS signals map to concurrency versus deploy lifecycle.
Operational check: Create a CloudWatch alarm approaching Lambda concurrency quotas, enable pipeline/deploy notifications to the same SNS topic used by on-call, and test both with a safe game day in a non-production account slice. Keep the civic/municipal context in mind: storm and enrollment peaks can burn concurrency quotas suddenly; deploy notices keep change windows auditable. Document the finding in the municipal incident ticket so the next on-call engineer inherits evidence rather than folklore.