A company uses an event-driven model with AWS Lambda and wants to reduce startup latency for functions that run on Java 11. The applications do not have strict latency requirements, but the company wants to reduce cold starts and outlier latencies when functions scale up. Which solution meets these requirements MOST cost-effectively?

Configuring Lambda SnapStart is the most cost-effective solution because it significantly reduces cold start times for Java functions without incurring additional charges for idle resources. SnapStart works by taking a snapshot of a pre-initialized function's memory and disk state, then resuming execution from that snapshot on subsequent invocations. This bypasses much of the typical startup overhead for Java runtimes. Increasing the timeout would not address cold starts; it only allows functions to run longer once started. Increasing memory can sometimes reduce cold starts marginally by providing more CPU, but it primarily improves execution speed and costs more. Provisioned concurrency guarantees zero cold starts but incurs charges for pre-allocated concurrency even when idle, making it less cost-effective for applications without strict latency requirements.