AWS Certified Developer – Associate (DVA-C02) — Question 156

A developer migrated a legacy application to an AWS Lambda function. The function uses a third-party service to pull data with a series of API calls at the end of each month. The function then processes the data to generate the monthly reports. The function has been working with no issues so far.

The third-party service recently issued a restriction to allow a fixed number of API calls each minute and each day. If the API calls exceed the limit for each minute or each day, then the service will produce errors. The API also provides the minute limit and daily limit in the response header. This restriction might extend the overall process to multiple days because the process is consuming more API calls than the available limit.

What is the MOST operationally efficient way to refactor the serverless application to accommodate this change?

Answer options

• A. Use an AWS Step Functions state machine to monitor API failures. Use the Wait state to delay calling the Lambda function.
• B. Use an Amazon Simple Queue Service (Amazon SQS) queue to hold the API calls. Configure the Lambda function to poll the queue within the API threshold limits.
• C. Use an Amazon CloudWatch Logs metric to count the number of API calls. Configure an Amazon CloudWatch alarm that stops the currently running instance of the Lambda function when the metric exceeds the API threshold limits.
• D. Use Amazon Kinesis Data Firehose to batch the API calls and deliver them to an Amazon S3 bucket with an event notification to invoke the Lambda function.

Correct answer: A

Explanation

Option A is the best choice as it allows for monitoring API failures and managing delays through AWS Step Functions, ensuring compliance with the API call limits. Options B and C do not effectively manage the pacing of API calls, potentially leading to errors. Option D introduces unnecessary complexity by batching calls instead of managing the execution flow directly.