Back to AWS Lambda

Event-driven architecture

5 minutes 5 Questions

Event-driven architecture is a pattern where components and services within an application communicate through the generation and processing of events. In AWS Lambda, a Lambda function is triggered in response to an event, concurrently processing it and invoking other services as needed. This enabl…

Test mode:
Start practice test
AWS Certified Solutions Architect - Event-driven architecture Example Questions

Test your knowledge of Event-driven architecture

Question 1

A company's operations team needs to be alerted with an email if the response time on their web applications increases beyond a certain threshold. Which AWS services can be combined to create such an event-driven architecture?

Correct Answer: Amazon CloudWatch and AWS Lambda

Using Amazon CloudWatch to monitor response times and then triggering an AWS Lambda function to send the email when the threshold is crossed can create an event-driven architecture that fulfills this requirement. The other options are not event-driven or not suitable for this scenario.

Question 2

A company stores user-uploaded videos in Amazon S3 and needs an event-driven solution that automatically initiates the transcoding workflow immediately after each upload. Which service should be used to react to S3 object-created events and start the processing pipeline?

Correct Answer: AWS Lambda with Amazon S3 triggers

AWS Lambda can be invoked directly by Amazon S3 ObjectCreated events, enabling an event-driven workflow that runs immediately when a video is uploaded. Lambda scales automatically and can either perform lightweight transcoding within its limits or, more commonly, initiate downstream transcoding jobs (e.g., submit to a media service or a queue) as part of the pipeline. AWS Batch and Amazon EC2 with Auto Scaling are not natively triggered by S3 uploads and require additional orchestration, and AWS Glue is designed for data ETL, not media transcoding.

Question 3

A social media company needs a serverless, event-driven solution to ingest a continuous stream of user comments and perform real-time sentiment analysis with low latency. Which AWS service combination is the best fit?

Correct Answer: AWS Lambda with Kinesis Data Streams

AWS Kinesis Data Streams provides a highly scalable, low-latency stream ingestion layer, and AWS Lambda can be configured as an event source consumer to process records as they arrive. This serverless, event-driven pairing enables real-time sentiment analysis by invoking Lambda functions per batch of records with millisecond latency, automatic scaling, and exactly-once processing semantics when implemented correctly. The Lambda code can call Amazon Comprehend for sentiment detection if needed. AWS Batch is designed for scheduled or batch workloads, not continuous real-time streaming. AWS Fargate runs containers but does not inherently provide a streaming/event-driven ingestion layer; you would still need a service like Kinesis or Kafka to achieve the required pattern. Amazon RDS with stored procedures is not suitable for high-throughput stream processing and would not scale or provide low-latency event-driven handling for sentiment analysis.

More Event-driven architecture questions
18 questions (total)
Start 18 question test