Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam BDS-C00 Topic 9 Question 96 Discussion

Actual exam question for Amazon's BDS-C00 exam
Question #: 96
Topic #: 9
[All BDS-C00 Questions]

A company is running a batch analysis every hour on their main transactional DB running on an RDS MySQL instance to populate their central Data Warehouse running on Redshift. During the execution of the batch their transactional applications are very slow. When the batch completes they need to update the top management dashboard with the new data. The dashboard is produced by another system running on-premises that is currently started when a manually-sent email notifies that an update is required The on-premises system cannot be modified because is managed by another team. How would you optimize this scenario to solve performance issues and automate the process as much as possible?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Sophia
5 months ago
I think both options have their merits. It ultimately depends on the specific requirements and constraints of the company. But I lean towards option D for its scalability and efficiency.
upvoted 0 times
...
Carlee
5 months ago
If I had a nickel for every time I had to integrate with a 'managed by another team' system, I'd be a rich person. Option B seems like the way to go, but I hope the on-premises team has a good sense of humor.
upvoted 0 times
...
Brittni
5 months ago
Ah, the joys of dealing with legacy systems. Option C with the RDS Read Replica might be the most straightforward approach here. At least it doesn't involve introducing a whole new database platform.
upvoted 0 times
Heike
4 months ago
Yeah, I agree. It's probably the least disruptive option for the on-premises system.
upvoted 0 times
...
Isabella
4 months ago
Option C with the RDS Read Replica sounds like a good idea. It keeps things simple.
upvoted 0 times
...
...
Myra
5 months ago
That's a good point, Brendan. Using a Read Replica can definitely improve performance. But wouldn't SNS be more reliable for notifications?
upvoted 0 times
...
Stevie
5 months ago
I'm not sure why they would need to replace the RDS instance with Redshift for the batch analysis. Seems like a bit of overkill. Option D looks like the simplest solution.
upvoted 0 times
Renea
4 months ago
Exactly, it would streamline the process and improve performance without the need for a complete overhaul.
upvoted 0 times
...
Colette
4 months ago
That way the on-premises system can be notified automatically without manual intervention.
upvoted 0 times
...
Tom
4 months ago
I agree, creating an RDS Read Replica for the batch analysis and using SQS to send a message seems like a good approach.
upvoted 0 times
...
Dottie
4 months ago
Option D looks like the simplest solution.
upvoted 0 times
...
...
Brendan
5 months ago
I disagree, I believe option D is better. Creating an RDS Read Replica will offload the batch analysis workload and SQS can efficiently send messages to update the dashboard.
upvoted 0 times
...
Myra
5 months ago
I think option A is the best choice. Redshift is optimized for analytics and SNS can easily notify the on-premises system.
upvoted 0 times
...
Mendy
5 months ago
Option B sounds the most promising. Using SQS to send a message to the on-premises system seems like a more reliable and scalable way to automate the update process.
upvoted 0 times
Goldie
4 months ago
I agree, SQS would definitely help streamline the process and reduce the manual effort required for updating the dashboard.
upvoted 0 times
...
Dong
4 months ago
Option B sounds the most promising. Using SQS to send a message to the on-premises system seems like a more reliable and scalable way to automate the update process.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77