Key points

• Lambda fits compatible runtimes, execution duration, event models, and ephemeral execution; durable state belongs outside the function.
• Memory selection affects available compute resources, so tune by measured duration and total work.
• Concurrency, retries, event-source semantics, connection pressure, and downstream limits are architecture responsibilities.

Best-known use cases

• Process events or API requests with short-lived functions.
• Run intermittent automation without idle servers.

What candidates often confuse it with

• Lambda runs functions; Fargate runs containers and EC2 provides host control.
• Lambda scales rapidly; SQS can buffer work to protect downstream dependencies.

Key takeaway

Choose Lambda for compatible event functions, then control concurrency and externalize state.

Related services

• Amazon API Gateway
• Amazon SQS
• AWS Step Functions
• AWS Fargate

Relevant exam tasks

• D2.1
• D3.2
• D4.2

Learn more

• AWS Lambda