MENU
An organization is designing an integration solution to replicate financial transaction data from a legacy system into a data warehouse (DWH).
The DWH must contain a daily snapshot of financial transactions, to be delivered as a CSV file. Daily transaction volume exceeds tens of millions of records, with significant spikes in volume during popular shopping periods.
What is the most appropriate integration style for an integration solution that meets the organization's current requirements?
Suggested Answer: A
Get Premium Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
MI
Mirta
10 months ago
Definitely leaning towards Batch-triggered ETL for efficiency!
TR
Trinidad
11 months ago
Wait, are we sure tens of millions of records can be processed daily?
KA
Katina
11 months ago
Event-driven architecture might be overkill for this use case.
YO
Youlanda
11 months ago
Sounds like Batch-triggered ETL is the way to go for daily snapshots.
HE
Heike
11 months ago
I think API-led connectivity could handle the spikes better.
ZA
Zana
11 months ago
Batch-triggered ETL seems to align with the requirement for a daily CSV file, but I wonder if it can handle the spikes effectively.
YO
Yoko
12 months ago
I practiced a similar question where API-led connectivity was mentioned, but I'm not convinced it's the best option for daily snapshots.
DO
Dorthy
12 months ago
I'm not entirely sure, but I feel like event-driven architecture could handle spikes in transaction volume better.
JO
Johnna
1 year ago
I remember studying about batch processing for large volumes of data, so I think Batch-triggered ETL might be a good fit here.
GR
Gracia
1 year ago
Event-driven architecture seems like an interesting option, but I'm not sure it's the most efficient way to handle the scale and frequency of the data updates. I'd lean more towards a batch-triggered ETL approach.
LE
Leigha
1 year ago
Based on the details provided, I think a batch-triggered ETL solution would be the most appropriate. It can handle the high volume and spikes, and the daily snapshot requirement fits well with a batch process.
GO
Golda
1 year ago
I'm a bit confused here. Microservices or API-led connectivity could also work, but I'd need to understand more about the legacy system and the data warehouse requirements.
AL
Alise
1 year ago
Hmm, not sure about that. With the daily snapshot requirement, an event-driven architecture might be a better fit to capture the changes in real-time.
PE
Penney
1 year ago
This looks like a classic data integration problem. I'd probably go with a batch-triggered ETL approach to handle the high transaction volume and spikes.
ER
Erinn
2 years ago
API-led connectivity? More like API-led confusion if you ask me. Batch ETL all the way, folks. It's the classic choice for a reason.
GW
Gwen
1 year ago
Event-driven architecture might be too complex for this scenario, batch ETL seems like the safer bet.
LO
Louvenia
1 year ago
I agree, it's a reliable and efficient choice for this kind of integration.
CL
Clare
1 year ago
Batch ETL is definitely the way to go for handling large volumes of data.
DE
Deeanna
2 years ago
I'm not sure why anyone would even consider microservices for this use case. That's like trying to build a skyscraper with toothpicks!
TO
Tommy
1 year ago
D) Batch-triggered ETL
RE
Reynalda
1 year ago
C) API-led connectivity
MI
Miles
1 year ago
A) Event-driven architecture
IR
Irma
2 years ago
Hmm, I don't think an event-driven architecture would work well here. The high transaction volume and need for a daily snapshot make a batch-triggered ETL the logical choice in my opinion.
CO
Cordelia
2 years ago
I'm leaning towards option D. With millions of records and spikes in volume, a batch-triggered ETL process seems like the most efficient way to handle the data load without risking performance issues.
MI
Mitsue
1 year ago
I agree with you. Option D seems like the best choice for handling such a large volume of data efficiently.
KA
Kallie
1 year ago
D) Batch-triggered ETL
MA
Matthew
1 year ago
C) API-led connectivity
PA
Pamella
2 years ago
B) Microservice architecture
NA
Nathalie
2 years ago
A) Event-driven architecture
MA
Malcom
2 years ago
That's a good point, but wouldn't Microservice architecture also be able to handle the daily snapshot requirement efficiently?
VI
Vincent
2 years ago
I disagree, I believe Event-driven architecture would be better for handling spikes in volume.
MA
Malcom
2 years ago
I think the most appropriate integration style would be Batch-triggered ETL.