AWS Serverless Architecture and AWS Lambda 5

Question 1

A developer wants to reuse common libraries across multiple Lambda functions without duplicating code. What is the recommended approach?

Accepted Answer

Use Lambda Layers to share common dependencies

Answer

Lambda Layers allow you to package shared libraries, dependencies, or custom runtimes separately and attach them to multiple functions.

Question 2

What happens to a Lambda function's environment variables when you publish a new version?

Accepted Answer

Environment variables are snapshotted and immutable in the published version

Answer

When you publish a Lambda version, the environment variables are included in the snapshot and become immutable for that specific version.

Question 3

A serverless application needs to fan out a single event to multiple downstream Lambda functions simultaneously. Which pattern is most appropriate?

Accepted Answer

Publish the event to SNS and subscribe multiple Lambda functions

Answer

SNS enables a fan-out pattern where a single published message is delivered to all subscribed Lambda functions simultaneously.

Question 4

Which Lambda concurrency type pre-warms execution environments to eliminate cold starts entirely?

Accepted Answer

Provisioned Concurrency

Answer

Provisioned Concurrency pre-initializes a specified number of execution environments so they are always ready to respond without cold start latency.

Question 5

A Lambda function is processing S3 events but occasionally fails and you want failed events routed to an SQS queue automatically. What feature enables this?

Accepted Answer

Lambda Destinations for asynchronous invocations

Answer

Lambda Destinations for asynchronous invocations allow you to route failed events to an SQS queue, SNS topic, EventBridge, or another Lambda function.

AWS Practice Test

AWS Practice Test

AWS Serverless Architecture and AWS Lambda 5