A grants Lambda extracts ZIPs into /tmp; later invokes on the same warm environment fail in odd ways. What resource problem fits?
Select an answer to reveal the explanation.
Short Explanation
/tmp on Lambda is a shared scratch pad for that warm box. Fill it extracting ZIPs and the next invokes on the same environment fail in mysterious ways until the sandbox is replaced.
Full Explanation
A grants Lambda that extracts ZIPs into /tmp and later fails oddly on the same warm environment likely exhausted ephemeral /tmp space. Lambda execution environments reuse /tmp across warm invokes; leftover extracts accumulate until subsequent invokes cannot write, producing confusing failures that disappear only when a fresh environment appears. Civic grant-document processing must clean temporary files or size work to the available ephemeral storage.
API Gateway stage variables do not cap /tmp to the deployment package size as a hidden storage controller.
DynamoDB eventually consistent reads do not delete /tmp after queries; temporary filesystem lifecycle is local to the execution environment.
SNS fan-out does not require attaching an EBS volume to each Lambda concurrent execution for normal ZIP extract use cases.
Exam caveat: /tmp is limited and persisted for the life of a warm environment—clean up and consider configured ephemeral storage size.
Operational check: Instrument free space before/after extract, delete temporary files in finally blocks, test large grant ZIPs under reserved concurrency, and confirm warm invokes remain stable. Keep the civic/municipal context in mind: grant season uploads spike ZIP sizes; leftover temp files turn into production incidents after the first few warm cycles.