Home › AWS Developer Associate › cloudcomputing › awsdevtroubleshooting › A Lambda function's 99th-percentile latency is d…
A Lambda function's 99th-percentile latency is dominated by cold starts. Which optimisation REDUCES (or eliminates) cold-start impact on user-facing requests?
ADisable CloudWatch logs to remove log-init time
BSet the timeout to 1 second so the cold start fails faster
CConfigure Provisioned Concurrency to keep N execution environments pre-initialised
DReduce the function's memory to the minimum
Answer & Solution
Correct answer: C. Configure Provisioned Concurrency to keep N execution environments pre-initialised
Provisioned Concurrency keeps init done off the request path. Reducing timeout doesn't eliminate cold starts. Logs init isn't dominant. Lower memory generally slows everything down.
Related questions
A serverless app's Lambda functions are billed per-millisecond. Which cost-optimization stWhich CloudWatch construct sends an SNS notification when a Lambda's error rate exceeds 5%An application sends events to an SQS queue. Suddenly the queue's `ApproximateNumberOfMessA Lambda function in a VPC hits an external HTTPS API. Cold starts now take 8+ seconds insA team needs to query Lambda logs ad-hoc with SQL-like syntax (filter by request id, errorWhich CloudWatch feature lets a developer build a dashboard showing graphs of multiple metA Lambda function called from API Gateway returns 502 Bad Gateway under load. Logs show "TA Lambda function intermittently exceeds its memory limit. The team has identified high me