A company hosts an internal serverless application using Amazon API Gateway and AWS Lambda. Employees report high latency when they start using the application each day. The company wants to reduce this latency. Which solution meets the requirement?

The correct solution is to set up scheduled scaling to increase Lambda provisioned concurrency. High latency at the start of the day suggests a "cold start" issue, where Lambda functions take longer to initialize due to infrequent use. Provisioned Concurrency keeps functions initialized and ready to respond, eliminating cold starts. Scheduling this before peak usage ensures employees experience low latency. Increasing API Gateway throttling limits would allow more requests but wouldn't address Lambda cold starts. Creating a CloudWatch alarm to invoke a Lambda function would trigger the function, but it wouldn't guarantee multiple instances are warm and ready for concurrent requests. Increasing Lambda function memory can improve execution speed for compute-intensive tasks but does not directly solve cold start latency for initial invocations.