The same grant-scoring Lambda code needs higher memory and longer timeout in load-test than in production. How should configuration differ across environments?
Select an answer to reveal the explanation.
Short Explanation
Load-test is a dress rehearsal with different stage lights—memory and timeout can differ without forking the business logic. Put those knobs in IaC or env-specific stacks, not magic numbers baked into source.
Full Explanation
Lambda configuration (memory, timeout, environment variables, concurrency) should be externalized per environment via infrastructure as code or environment-specific stacks. That keeps function code identical while allowing load-test headroom versus production guardrails. Hardcoding values in source or commit messages couples config to code and invites mistakes.