Examkin

Question

Difficulty: MediumServerless and Automated Scaling Architectures for Cost Efficiency

An insurance firm is designing a serverless system to process customer claims. The system receives claim applications that must be processed in the exact sequence they are submitted to prevent audit trail errors. The processing involves two steps: first, parsing and extracting metadata from the claim application (which takes less than 2 seconds); second, running a continuous claim verification model that analyzes historical database patterns over several hours. Which two AWS configurations will meet these requirements most cost-effectively? (Select two.)

  1. Configure an Amazon Simple Queue Service (Amazon SQS) FIFO queue to receive the claim applications and preserve message ordering.Answer
  2. Use an Amazon Elastic Container Service (Amazon ECS) service on AWS Fargate to run the continuous claim verification model.Answer
  3. C
    Configure an Amazon SQS standard queue to receive the claim applications to maximize throughput.
  4. D
    Use an AWS Lambda function to run the continuous claim verification model.
  5. E
    Provision an Amazon DynamoDB table in Provisioned Capacity Mode to act as a buffer for the incoming claim applications.

Answer

Configure an Amazon SQS FIFO queue to receive the claim applications and preserve message ordering, and use an Amazon ECS service on AWS Fargate to run the continuous claim verification model.
To process claim applications in the exact sequence they are submitted, the architecture must utilize an Amazon SQS FIFO queue, which guarantees first-in, first-out delivery. For the claim verification model, because the process runs continuously for several hours, deploying the application as a container task on Amazon ECS with AWS Fargate is the most cost-effective and viable choice. Fargate provides a serverless execution environment with no time limit, unlike AWS Lambda, which is restricted to 15 minutes.

Step-by-Step Solution

1
Analyze ordering requirements for message ingestion
The scenario requires claim applications to be processed in the exact sequence they are submitted. This dictates the use of a first-in, first-out (FIFO) queue.
Standard queues do not guarantee strict message ordering.
2
Select the appropriate queue type
Choose Amazon SQS FIFO queue over standard SQS or DynamoDB buffers.
An Amazon SQS FIFO queue natively supports messaging ordering, scales automatically, and incurs cost only when requests are made.
3
Analyze execution duration for the verification model
The claim verification model runs continuously for several hours.
AWS Lambda is limited to a 15-minute timeout and is cost-inefficient for continuous execution.
4
Select the compute platform for the long-running task
Choose Amazon ECS on AWS Fargate for containerized execution.
Fargate allows running containers for hours without managing underlying EC2 hosts, optimizing both operational overhead and cost for long-running processes.

Key Concept

Decoupling components using SQS FIFO queues for sequence preservation while pairing with containerized compute (Fargate) for long-running processes to optimize architectural cost and reliability.
Estimated Time:2m 0s
Rate this question

Topics

Serverless and Automated Scaling Architectures for Cost Efficiency