New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon SAA-C03 Exam - Topic 1 Question 68 Discussion

Actual exam question for Amazon's SAA-C03 exam
Question #: 68
Topic #: 1
[All SAA-C03 Questions]

A company is designing an application on AWS that provides real-time dashboards. The dashboard data comes from on-premises databases that use a variety of schemas and formats. The company needs a solution to transfer and transform the data to AWS with minimal latency.

Which solution will meet these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: A

Amazon MSK is a fully managed, highly available Apache Kafka service for streaming data with low latency. Kafka Connect and stream processors enable ingest from heterogeneous sources and perform in-stream transformation before delivery to consumers (e.g., the dashboard service). This satisfies real-time updates from diverse schemas and formats. Kinesis alternatives could work, but among the given choices, MSK is the only streaming option designed for sub-second, continuous pipelines. Kinesis Data Firehose (B) buffers and batches data to S3 and is optimized for delivery to storage, not low-latency dashboards. AWS DMS schema conversion (C) focuses on database migration, not ongoing real-time, multi-format streaming for dashboards. AWS DataSync (D) is for file/object transfer, not database change streams. Hence, MSK best meets minimal-latency, transform-in-flight needs with managed operations.


Contribute your Thoughts:

0/2000 characters
Janessa
3 days ago
Hmm, Option B might work, but the periodic data import could introduce some latency.
upvoted 0 times
...
Jina
8 days ago
Option C looks interesting, but I'm not sure about the complexity of the Lambda function and EventBridge scheduling.
upvoted 0 times
...
Launa
13 days ago
I'm leaning towards Option D. DataSync seems like a straightforward way to handle the continuous data transfer.
upvoted 0 times
...
Wava
18 days ago
Option A seems like a good fit for real-time data transfer and transformation.
upvoted 0 times
...
Rory
23 days ago
AWS DataSync sounds familiar, but I can't recall if it supports continuous data transfer. I need to double-check that.
upvoted 0 times
...
Merilyn
28 days ago
I practiced a similar question where Data Firehose was mentioned, but it seemed more suited for batch processing rather than real-time updates.
upvoted 0 times
...
Zack
1 month ago
I think using Amazon MSK could work since it handles streaming data well, but I wonder if it might add complexity with the different schemas.
upvoted 0 times
...
Francesco
1 month ago
I remember studying about AWS DMS and how it can help with schema conversion, but I'm not sure if it's the best fit for real-time dashboards.
upvoted 0 times
...
Theron
1 month ago
I'm leaning towards option B with Amazon Firehose. Transferring the data to S3 first and then having the dashboard app pull from there seems like a straightforward approach.
upvoted 0 times
...
Mozelle
2 months ago
Option C with the AWS DMS and Lambda function sounds like a good way to consolidate the data sources, but I'm not sure if that would meet the low-latency requirement.
upvoted 0 times
...
Jin
2 months ago
I'm a bit confused by the different options. Can Amazon MSK really handle the data transformation part, or is that just for the data transfer?
upvoted 0 times
...
Cassie
2 months ago
I think option D looks the most promising. AWS DataSync seems like it could handle the real-time data transfer and transformation requirements.
upvoted 0 times
...

Save Cancel