You have set a Lambda function timeout to 10 seconds. The function runs longer than 10 seconds. What is the result?
Think about how time limits protect resources in cloud functions.
When a Lambda function runs longer than its configured timeout, AWS forcibly stops it and returns a timeout error. This prevents runaway costs and resource use.
You want to run a Lambda function every day at 8 AM automatically. Which AWS service should you use to trigger it?
Think about services that can schedule tasks or events.
Amazon EventBridge (formerly CloudWatch Events) can create rules to trigger Lambda functions on schedules like cron expressions.
You want your Lambda function to read files from a specific S3 bucket. Which approach follows the best security practice?
Consider the principle of least privilege and secure credential management.
Assigning a specific IAM role with limited permissions to the Lambda function is secure and follows best practices. Embedding keys or making buckets public is insecure.
You increase the memory setting of a Lambda function from 128 MB to 1024 MB. What changes occur?
Think about how AWS bundles CPU with memory for Lambda functions.
In AWS Lambda, CPU power scales with memory allocation. Increasing memory also increases CPU, which can speed up execution.
You need to store database passwords for your Lambda function securely. What is the best practice?
Consider secure storage and retrieval of secrets in AWS.
Using AWS Secrets Manager or Parameter Store with encryption is the best practice to keep sensitive data secure and separate from code.