SAA-C03 · Question #434
A company is designing a solution to capture customer activity on the company's web applications. The company wants to analyze the activity data to make predictions. Customer activity on the web appli
The correct answer is C. Deploy an Amazon API Gateway endpoint in front of an Amazon Data Firehose delivery stream.. The requirements specify capturing unpredictable and sudden spikes in customer activity, integrating easily with other web applications, and including authorization. Amazon API Gateway with Lambda authorizer provides a secure, scalable entry point with flexible authorization mech
Question
A company is designing a solution to capture customer activity on the company's web applications. The company wants to analyze the activity data to make predictions. Customer activity on the web applications is unpredictable and can increase suddenly. The company requires a solution that integrates with other web applications. The solution must include an authorization step. Which solution will meet these requirements?
Options
- ADeploy a Gateway Load Balancer (GWLB) in front of an Amazon Elastic Container Service
- BDeploy an Amazon API Gateway endpoint in front of an Amazon Kinesis data stream. Store the
- CDeploy an Amazon API Gateway endpoint in front of an Amazon Data Firehose delivery stream.
- DDeploy a Gateway Load Balancer (GWLB) in front of an Amazon Elastic Container Service
How the community answered
(46 responses)- A7% (3)
- B4% (2)
- C76% (35)
- D13% (6)
Explanation
The requirements specify capturing unpredictable and sudden spikes in customer activity, integrating easily with other web applications, and including authorization. Amazon API Gateway with Lambda authorizer provides a secure, scalable entry point with flexible authorization mechanisms including token validation. Amazon Kinesis Data Firehose is a fully managed service to reliably load streaming data into destinations such as Amazon S3, which fits well for capturing streaming customer activity data. API Gateway integrates natively with Firehose for direct ingestion. This combination supports unpredictable traffic, smooth scaling, and simple authorization. Option B uses Kinesis Data Streams, which requires more management than Firehose and is less optimized for direct API integration. Options A and D use Gateway Load Balancer and ECS containers plus EFS, which add complexity and are less suited for unpredictable traffic with integrated authorization.
Community Discussion
No community discussion yet for this question.