A county Lambda in production writes DEBUG logs with infinite CloudWatch Logs retention, driving cost and widening exposure of sensitive permit fields. What should the developer change?
Select an answer to reveal the explanation.
Short Explanation
Infinite DEBUG in prod is like leaving every hallway light on with the doors unlocked—pricey and leaky. Turn the volume down to what operators need and put a retention clock on the log group. You still keep enough history without forever storing sensitive permit chatter.
Full Explanation
Production logging should use severity appropriate to the environment and a retention period aligned with operational and data-classification needs. Infinite retention of verbose DEBUG output increases cost and expands the window of sensitive-data exposure in CloudWatch Logs. Encryption alone does not fix verbosity or retention; mirroring to DynamoDB without TTL or deleting groups each deploy is not a sound retention strategy.