Home › AWS Developer Associate › cloudcomputing › awsdevelopment › Which Lambda configuration setting most directly…
Which Lambda configuration setting most directly affects the function's CPU and network performance, not just the memory ceiling?
AFunction timeout in seconds
BThe runtime version (Node 22 vs Node 20)
CMemory allocation (MB) — Lambda allocates CPU and network proportionally to configured memory
DWhether layers are attached
Answer & Solution
Correct answer: C. Memory allocation (MB) — Lambda allocates CPU and network proportionally to configured memory
Lambda's memory setting also scales CPU and network — this is why "increase memory to get more CPU" is a classic tuning move. Timeout caps how long a single invocation may run; layers are deps; runtime affects language semantics but not the CPU/RAM ratio.
Related questions
A Lambda function reads from a Kinesis Data Stream. Throughput is fine on average but spikAn API Gateway REST API in front of Lambda needs to authenticate requests using a Cognito Which strategy allows a Lambda function inside a VPC to access the internet (e.g., to callA serverless app needs to fan out a single event to multiple downstream Lambda functions, A Lambda function processes a large file from S3. Cold starts are unacceptably long on JavWhich AWS feature lets developers attach short-lived AWS credentials to a Lambda function What does it mean for an API endpoint to be IDEMPOTENT?A Lambda function is processing messages from an SQS queue. Some messages fail repeatedly.