Bird
0
0

You wrote a serverless function but it fails to handle sudden traffic spikes, causing errors. What is the likely cause?

medium📝 Debug Q14 of 15
AWS - Lambda
You wrote a serverless function but it fails to handle sudden traffic spikes, causing errors. What is the likely cause?
AThe function has a fixed number of instances and does not auto-scale.
BServerless functions automatically scale, so the error is unrelated to scaling.
CThe function's timeout setting is too high.
DThe function is not connected to a database.
Step-by-Step Solution
Solution:

  1. Step 1: Understand serverless scaling

    Serverless functions usually auto-scale, but concurrency limits or misconfigurations can restrict it to a fixed number of instances.

  2. Step 2: Identify cause of errors

    If the function does not scale beyond a fixed number, it cannot handle traffic spikes, causing errors.

  3. Final Answer:

    The function has a fixed number of instances and does not auto-scale. -> Option A

  4. Quick Check:

    Scaling limits cause errors under load [OK]
Quick Trick: Check if auto-scaling limits block traffic handling [OK]
Common Mistakes:
  • Assuming serverless always scales without limits
  • Blaming timeout when scaling is the issue
  • Ignoring connection issues unrelated to scaling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
API Gateway - Resources and methods - Quiz 7medium API Gateway - API keys and usage plans - Quiz 15hard API Gateway - CORS configuration - Quiz 9hard AWS Lambda - Creating a Lambda function - Quiz 10hard Auto Scaling - Cooldown periods - Quiz 6medium Auto Scaling - Auto Scaling with ELB integration - Quiz 11easy Auto Scaling - Predictive scaling overview - Quiz 6medium DynamoDB - DynamoDB Streams overview - Quiz 15hard Elastic Load Balancing - Cross-zone load balancing - Quiz 9hard Elastic Load Balancing - Why load balancing matters - Quiz 1easy