Deal of The Day! 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

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?
A) Integrate the dashboard with Amazon Managed Streaming for Apache Kafka (Amazon MSK) to transfer and transform the data from the on-premises databases to the dashboards.
B) Use Amazon Data Firehose to transfer the data to an Amazon S3 Bucket. Configure the dashboard application to import new data from the S3 bucket periodically.
C) Use AWS Database Migration Service (AWS DMS) Schema Conversion to consolidate the on-premises databases into a single AWS database. Use an AWS Lambda function that is scheduled by Amazon EventBridge to transfer data from the consolidated database to the dashboard application.
D) Use AWS DataSync to transfer data from the source databases to the dashboard application continuously. Configure the dashboard application to import data from DataSync.

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
Laila
1 month ago
I’m leaning towards B. S3 is reliable for data storage.
upvoted 0 times
...
Pete
1 month ago
Option A could work too, but it seems complex.
upvoted 0 times
...
An
2 months ago
I prefer option D. Continuous transfer sounds efficient.
upvoted 0 times
...
Desire
2 months ago
I think option C is the best. Consolidating databases makes sense.
upvoted 0 times
...
Vincenza
2 months ago
Totally agree with Lindsay, C is the way to go!
upvoted 0 times
...
Kendra
2 months ago
Wait, can DataSync really handle all those formats?
upvoted 0 times
...
Bettyann
2 months ago
D seems like the best choice for continuous transfer!
upvoted 0 times
...
Daryl
3 months ago
I think B is too slow for real-time needs.
upvoted 0 times
...
Lindsay
3 months ago
Option C sounds solid for schema conversion!
upvoted 0 times
...
Annita
3 months ago
Option C sounds like a lot of work. I'd rather keep it simple with Option D.
upvoted 0 times
...
Ryann
3 months ago
Option A all the way! Kafka is the way to go for real-time streaming.
upvoted 0 times
...
Janessa
4 months ago
Hmm, Option B might work, but the periodic data import could introduce some latency.
upvoted 0 times
...
Jina
4 months ago
Option C looks interesting, but I'm not sure about the complexity of the Lambda function and EventBridge scheduling.
upvoted 0 times
...
Launa
4 months ago
I'm leaning towards Option D. DataSync seems like a straightforward way to handle the continuous data transfer.
upvoted 0 times
...
Wava
4 months ago
Option A seems like a good fit for real-time data transfer and transformation.
upvoted 0 times
...
Rory
4 months 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
5 months 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
5 months 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
5 months 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
5 months 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
5 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
5 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
6 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
Gearldine
1 month ago
I agree, option D seems efficient for continuous data transfer.
upvoted 0 times
...
...

Save Cancel