[Solved] Why might a Lambda function experience a cold start delay? — Ans: Because the execution environment is created fresh for the first invocation | AWS

AWS - Lambda

Why might a Lambda function experience a cold start delay?

ABecause the function code is always loaded from S3 on every call

BBecause the execution environment is created fresh for the first invocation

CBecause Lambda runs on dedicated hardware per function

DBecause the function is waiting for manual approval

Step-by-Step Solution

Solution:

Step 1: Understand cold start concept
Cold start happens when Lambda creates a new execution environment for the first time, causing delay.
Step 2: Rule out incorrect reasons
Code is cached after first load, Lambda uses shared hardware, and no manual approval is needed.
Final Answer:
Because the execution environment is created fresh for the first invocation -> Option B
Quick Check:
Cold start = fresh environment creation delay [OK]

Quick Trick: Cold start = first-time environment setup delay [OK]

Common Mistakes:

MISTAKES

Master "Lambda" in AWS

9 interactive learning modes - each teaches the same concept differently

More AWS Quizzes

Why might a Lambda function experience a cold start delay?