Increase the configured CPU value
Increase the configured timeout value
Increase the configured memory value
Increase the configured concurrency value
blocks
layers
aliases
handlers
in sequence
both of these answers
neither of these answers
in parallel
aws lambda invoke --function ReturnBucketName outputfile.txt
aws lambda execute --function-name ReturnBucketName outputfile.txt
aws lambda invoke --function-name ReturnBucketName outputfile.txt
aws lambda execute --function ReturnBucketName outputfile.txt
AWS Trace
CloudStack
CloudTrail
AWS X-Ray
Create configuration files and deploy them using AWS CodePipeline.
Create CloudFormation templates and deploy them using AWS CodeBuild
Create configuration file and deploy using AWS CodeBuild
Create CloudFormation templates and deploy them using AWS CodePipeline.
API Gateway
S3
SAS
CloudTrail
Use S3 metrics and CloudWatch alarms
Create custom metrics within your Lambda code.
Create custom metrics within your CloudWatch code.
Use Lambda metrics and CloudWatch alarms.
an SSL certificate
a bitmask
an AWS KMS key
an HTTP protocol
binaries.
all of these answers
executables
Shell scripts
MVC
virtual
stateless
protocol
by uploading a .zip file
all of these answers
by editing inline
from an S3 bucket
CLoudWatch logs
DynamoDB logs
S3 logs
Lambda logs.
CodeStack
ElasticStack
Mobile Hub
CodeDeploy
proportionally
equally
periodically
daily
resources and users
resources and conditions
events and users
events and conditions
logging streams
rotating streams
logging events
advancing log groups
create a Lambda
be an event source
assign an IAM role
delete a Lambda
Create a Lambda function with a custom runtime and reference the function in your Lambda
Create a Lambda layer with a custom runtime and reference the layer in your lambda
You cannot use Lambda in this situation
Create a Lambda function with a custom runtime
the execution policy
the Lambda configuration
the Lambda nodes
the IAM user
department:Sales,department:Sales
department:Sales,department:sales
aws:demo;aws:demo
aws:demo;aws:DEMO
_
.neither of these answers
UDP/IP
TCP/IP
both of these answers
automatically
none of these answers
manually
ad hoc
stream and record sizes
stream and shard sizes
batch and record sizes
batch and shard sizes
Place each subnet in a VPC. Associate all subnets to your Lambda.
Place all subnets in a VPC. Associate all subnets to your Lambda.
Configure your Lambda to be available to multiple VPCs.
Configure all application VPCs to be peered.
number of function calls
amount of code run
compute time
amount of infrastructure used
Author a Lambda from scratch.
Use a blueprint.
Use a .zip deployment package.
Use the serverless app repository.
/tmp
/default
/temp
/ds
Delete the function.
Set the function concurrent execution limit to 0 while you update the code.
Reset the function.
Set the function concurrent execution limit to 100 while you update the code.
Overprovision memory to run your functions faster and reduce your costs. Do not overprovision your function timeout settings.
Overprovision memory and your function timeout settings to run your functions faster and reduce your costs.
Do not overprovision memory. Overprovision your function timeout settings to run your functions faster and reduce costs.
Do not overprovision memory. Do not overprovision your function timeout settings to run your functions faster and reduce costs.
removing log groups
none of these answers
creating log groups
updating log groups
DynamoDB tables
key-value pairs
S3 buckets
none of these answers
S3
API Gateway
X-Ray
DynamoDB
in the Lambda function code
in a Lambda environment variable
in the Lambda tags
in another S3 bucket
Deploy the Lambda
Export the function
none of these answers
Configure a test event
Fleece
NPM
none of these answers
Pod
CloudTrail
CloudWatch
CloudFormation
LogWatch
a table definition
queue isolation
STS Write
an SNS topic
POST
"All object create events"
PUT
COPY
Lambda configuration from logging code
Lambda handler from logging code
Lambda handler from core logic
Lambda configuration from core logic
YAML definition
CloudFormation stack configuration
SAML deployment stack
Zip file of all related files
only at creation
only before deployment
never
anytime via configuration
EdgeCloud
CloudEdge
CloudFront
CloudStack
custom
all of these answers
Java
Ruby
[Reference](https://aws.amazon.com/blogs/compute/new-for-aws-lambda-predictable-start-up-times-with-provisioned-concurrency/
Explanation Lambda can used for all services mentioned on the question: Kinesis, S3, SNS, SQS, DynamoDB. But as you can see in the reference, Lambda's responsibility and method invocation can be categorized by Lambda polling and Event Driven (synchronous invocation). When you implement an event-driven architecture, you grant the event-generating service permission to invoke your function in the function's resource-based policy. Then you configure that service to generate events that invoke your function. When you implement a Lambda polling architecture, you grant Lambda permission to access the other service in the function's execution role. Lambda reads data from the other service, creates an event, and invokes your function. According to this analytics, Kinesis-DynamoDB-SQS use same method invocation, Lambda polling.
Explanation (source google)
With DynamoDB Streams, you can trigger a Lambda function to perform additional work each time a DynamoDB table is updated. Lambda reads records from the stream and invokes your function synchronously with an event that contains stream records.
These events are considered synchronous events. Simply put, it means that when somebody is calling an API Gateway, it will trigger your Lambda function. It's a synchronous event because your Lambda function has to respond to the client directly at the end of its invocation.
You can use Lambda to process event notifications from Amazon Simple Storage Service. Amazon S3 can send an event to a Lambda function when an object is created or deleted.