Q12 — AWS SAA-C03 Ch.16

Question 12 of 100 | ← Chapter 16

Q1212. 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?

Correct Answer: C. Deploy an Amazon APl Gateway endpoint in front of an Amazon Data Firehose delivery stream.Store the data in an Amazon S3 bucket. Use an APl Gateway Lambda authorizer to handle authorization.

Explanation

To meet the company's requirements of capturing customer activity on web applications, analyzing the activity data to make predictions, and integrating with other web applications while including an authorization step, the most suitable solution is:C. Deploy an Amazon API Gateway endpoint in front of an Amazon Kinesis Data Firehose delivery stream. Store the data in an Amazon S3 bucket. Use an API Gateway Lambda authorizer to handle authorization.Analysis:Amazon API Gateway:Integration and Authorization: API Gateway serves as a front door for applications to access data, business logic, or functionality from your back-end services. It can integrate with various AWS services, including Kinesis Data Firehose, and provides built-in support for authorization through Lambda authorizers. Handling Unpredictable Traffic: API Gateway is designed to handle unpredictable traffic patterns, making it suitable for scenarios where customer activity can increase suddenly.Amazon Kinesis Data Firehose:Data Ingestion: Kinesis Data Firehose is a fully managed service for delivering real-time streaming data to destinations such as Amazon S3. It can capture, transform, and load streaming data into Amazon S3 for further analysis.Scalability: Kinesis Data Firehose automatically scales to match the throughput of your incoming data, making it suitable for handling sudden increases in customer activity.Amazon S3:Data Storage: S3 provides scalable, durable, and secure object storage for storing the customer activity data captured by Kinesis Data Firehose.Analysis and Predictions: The data stored in S3 can be analyzed using various AWS services, such as Amazon Athena, Amazon Redshift, or AWS Glue, to make predictions based on customer activity.API Gateway Lambda Authorizer:Authorization: A Lambda authorizer is an API Gateway feature that uses a Lambda function to control access to your API. It can be used to implement custom authorization logic, such as validating tokens or checking user permissions, before allowing requests to proceed to the back-end services.Why Other Options Are Not Suitable:A. Deploy a Gateway Load Balancer (GWLB) in front of an Amazon ECS container instance:Incorrect Use of GWLB: A Gateway Load Balancer is typically used for network-level load balancing and security, not for capturing and analyzing customer activity data. Lack of Authorization: This option does not mention any mechanism for handling authorization, which is a requirement for the company.B. Deploy an Amazon API Gateway endpoint in front of an Amazon Kinesis data stream:Data Stream vs. Data Firehose: While Kinesis Data Streams can capture and process streaming data, Kinesis Data Firehose is more suitable for delivering streaming data to destinations like S3 for further analysis, as it provides built-in transformation and delivery capabilities. Authorization Handling: Although this option mentions using an AWS Lambda function to handle authorization, it does not specify that the Lambda function would be used as an API Gateway Lambda authorizer, which is a more integrated and scalable solution. D. Deploy a Gateway Load Balancer (GWLB) in front of an Amazon ECS container instance with AWS Lambda for Authorization:Incorrect Use of GWLB: Similar to option A, a Gateway Load Balancer is not the appropriate tool for capturing and analyzing customer activity data.Lack of Data Ingestion and Storage: This option does not mention any mechanism for ingesting and storing the customer activity data, which is a key requirement for the company.