A Lambda-based application must have minimal latency and predictable start times. All environment setup must complete before each invocation. Which solution satisfies these requirements?

The correct solution is to publish a new version of the function and configure provisioned concurrency. Provisioned concurrency pre-initializes a specified number of execution environments, ensuring they are ready to respond immediately to invocations, thus eliminating cold starts and minimizing latency. Setting the function memory to its maximum and invoking it every minute with an EventBridge rule attempts to keep the environment warm, but it's not guaranteed to prevent cold starts for all invocations, especially during traffic spikes, and it incurs unnecessary costs. Optimizing static initialization code and reducing package size helps reduce cold start duration but doesn't eliminate cold starts entirely. Setting reserved concurrency to the account's maximum only limits the number of concurrent invocations; it doesn't pre-initialize environments or eliminate cold starts. Running setup steps manually before the first invocation is not an automated or scalable solution for a Lambda-based application.