Examkin

Soru

Zorluk: OrtaServerless and Automated Scaling Architectures for Cost Efficiency

A financial technology company is designing a serverless payment processing system. The system must process transactional ledger updates in the exact sequence they are received. The transaction volume is highly unpredictable, ranging from zero transactions for hours to sudden bursts of thousands of transactions per minute. Additionally, the system must run a nightly reconciliation report that processes all transaction data for the day. This report is computationally intensive and takes approximately 45 minutes to execute. Which two options should the solutions architect choose to design a highly cost-effective and automated scaling architecture? (Select two.)

  1. Configure an Amazon SQS FIFO queue to receive the transactional ledger updates and trigger AWS Lambda functions for processing.Cevap
  2. B
    Configure an Amazon SQS standard queue to receive the transactional ledger updates and trigger AWS Lambda functions for processing.
  3. Run the nightly reconciliation report as a containerized task on Amazon ECS with AWS Fargate using Fargate Spot capacity providers.Cevap
  4. D
    Run the nightly reconciliation report as an AWS Lambda function triggered by an Amazon EventBridge scheduled rule.
  5. E
    Store the ledger updates in an Amazon DynamoDB table configured with provisioned capacity mode to handle peak write workloads.

Cevap

Configure an Amazon SQS FIFO queue to receive the transactional ledger updates and trigger AWS Lambda functions for processing, and run the nightly reconciliation report as a containerized task on Amazon ECS with AWS Fargate using Fargate Spot capacity providers.
For the transaction updates, configuring an Amazon SQS FIFO queue ensures that messages are processed in strict chronological order, while AWS Lambda scales automatically to handle traffic spikes and costs nothing when there are no transactions. For the nightly reconciliation report, which runs for 45 minutes and is computationally intensive, Amazon ECS with AWS Fargate is ideal because Fargate only charges for resources while the container is running. Leveraging Fargate Spot capacity providers provides massive discounts, making it the most cost-effective option since the runtime exceeds AWS Lambda's 15-minute timeout.

Adım Adım Çözüm

1
Analyze the ordering and scalability requirements for transactional updates.
The updates require strict sequential order and must handle highly unpredictable bursts.
Amazon SQS FIFO queues guarantee first-in, first-out ordering, and AWS Lambda scales automatically from zero to meet demand, offering cost-optimal serverless compute.
2
Analyze the execution duration and cost requirements of the nightly report.
The report runs for 45 minutes daily and is computationally intensive.
Since the runtime exceeds the 15-minute AWS Lambda timeout limit, containerized tasks on Amazon ECS with AWS Fargate must be used. Fargate Spot offers significant cost savings for fault-tolerant batch workloads.

Anahtar Kavram

Combining serverless message queues (SQS FIFO) and auto-scaling compute (Lambda and Fargate Spot) to design cost-efficient architectures based on execution duration and ordering constraints.
Bu soruyu puanla

Konular

Serverless and Automated Scaling Architectures for Cost Efficiency