A global ad-tech corporation is deploying a real-time bidding (RTB) exchange on AWS. The platform must process up to incoming bid requests per second during peak traffic periods, with an end-to-end processing latency budget of per request. The architecture requires querying a user profile store with sub-millisecond read latency to enrich each bid request. In addition, the system must capture and persist transactional bid logs for downstream offline processing, analytics, and compliance audits without blocking the synchronous request-response flow. The platform must dynamically and instantly scale to accommodate sudden traffic bursts.
Which combination of architectural options will satisfy these performance, scalability, and latency requirements? (Select TWO.)
- Deploy a Network Load Balancer (NLB) to distribute incoming traffic to the application tier hosted on Amazon ECS with AWS Fargate using the AWS VPC (awsvpc) network mode.Answer
- Use Amazon DynamoDB with Amazon DynamoDB Accelerator (DAX) to store user profile data, configuring the application to query the DAX cluster for user attributes.Answer
- CDeploy an Application Load Balancer (ALB) to distribute incoming traffic, and configure AWS Auto Scaling with Target Tracking policies based on the RequestCountPerTarget metric to scale the backend tasks during sudden traffic spikes.
- DStore the user profile store in an Amazon RDS for PostgreSQL database configured with Multi-AZ, and configure the application to direct read queries to the standby instance in the secondary Availability Zone.
- EInvoke synchronous AWS Lambda functions behind an Amazon API Gateway to evaluate each bid request, utilizing the default regional concurrency pool to handle sudden traffic peaks.