You've learned about AWS Lambda and its event-driven, pay-per-execution model. Now let's practice identifying scenarios where serverless functions are the perfect fit.
Engagement Message
Ready to become a serverless expert?
Type
Multiple Choice
Practice Question
A photo-sharing app needs to automatically resize images when users upload them. The resizing happens only when photos are uploaded, which could be once per day or hundreds of times per hour. Which compute approach is most cost-effective?
A. Always-on EC2 instances waiting for uploads B. Containers that scale with traffic C. Lambda functions triggered by file uploads D. A dedicated image processing server
Suggested Answers
- A
- B
- C - Correct
- D
Type
Sort Into Boxes
Practice Question
Sort these characteristics into whether they describe Lambda or traditional servers:
Labels
- First Box Label: Lambda Functions
- Second Box Label: Traditional Servers
First Box Items
- Event-driven
- Pay per execution
- Automatic scaling
Second Box Items
- Always running
- Fixed monthly cost
- Manual scaling
Type
Fill In The Blanks
Markdown With Blanks
Fill in the blanks:
Lambda is ideal for [[blank:short-running]] tasks that run in response to events, while traditional servers are better for [[blank:long-running]] applications that need to run continuously.
