When triggered with event {}, it throws a KeyError. How can you fix it?
medium
A. Use event.get('message', 'No message') instead of event['message']
B. Remove the return statement
C. Add a print statement before return
D. Change function name to lambda_handler
Solution
Step 1: Identify cause of KeyError
Accessing event['message'] when 'message' key is missing causes KeyError.
Step 2: Use safe access method
Replacing event['message'] with event.get('message', 'No message') avoids error by providing default.
Final Answer:
Use event.get('message', 'No message') instead of event['message'] -> Option A
Quick Check:
Use get() to avoid KeyError on missing keys [OK]
Hint: Use get() with default to prevent KeyError [OK]
Common Mistakes:
Ignoring missing key causes error
Thinking print fixes KeyError
Assuming function name affects key access
5. You want an AWS Lambda function to process image uploads to S3 and resize them. Which combination of AWS services and Lambda features is best suited for this task?
hard
A. Use Lambda to create EC2 instances that resize images
B. Run Lambda on a schedule to scan S3 and resize images manually
C. Upload images directly to Lambda storage for resizing
D. Use S3 event trigger on object creation to invoke Lambda, which resizes images and saves back to S3
Solution
Step 1: Understand event-driven processing
S3 can trigger Lambda automatically when new objects are created, ideal for immediate processing.
Step 2: Evaluate options for image resizing
Use S3 event trigger on object creation to invoke Lambda, which resizes images and saves back to S3 uses S3 event triggers and Lambda to resize and save images back to S3, which is efficient and serverless. Run Lambda on a schedule to scan S3 and resize images manually delays processing and requires scanning. Use Lambda to create EC2 instances that resize images misuses Lambda to create servers. Upload images directly to Lambda storage for resizing is invalid as Lambda has no persistent storage for uploads.
Final Answer:
Use S3 event trigger on object creation to invoke Lambda, which resizes images and saves back to S3 -> Option D
Quick Check:
S3 event triggers + Lambda = best for image processing [OK]
Hint: Use S3 event triggers to run Lambda on uploads [OK]
Common Mistakes:
Thinking Lambda can store files persistently
Using scheduled scans instead of event triggers
Misusing Lambda to create servers
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.