Q: 20
A development learn has an Amazon API Gateway REST API that is backed by an AWS Lambda
function.
Users have reported performance issues for the Lambda function. The development team identified
the source of the issues as a cold start of the Lambda function. The development team needs to
reduce the time needed for the Lambda function to initialize.
Which solution will meet this requirement?
Options
Discussion
D , C is tempting but doesn't really prevent cold starts, just speeds them up a tiny bit. Provisioned concurrency (D) actually handles the cold start directly. Seen similar on practice tests.
C doesn't really solve cold starts, just makes the function run faster after it starts. D is the way to go because provisioned concurrency pre-warms Lambda instances. Pretty sure that's what AWS recommends for this scenario, but open to other views.
D is the right call. Provisioned concurrency actually keeps Lambda warm, so cold starts get eliminated. C (upping memory) helps a bit but doesn’t guarantee a warm start like D. Pretty sure that’s what AWS exams expect.
D imo, storing creds in an encrypted .txt on S3 should work since S3 can encrypt files and you can control access. I don't see why you'd need Parameter Store here. Anyone else thinks D could fit?
Be respectful. No spam.
Question 20 of 35