MENU
The retrieveBalances flow in the Mule application is designed to use an operation in a connector to the Finance system (the Finance operation) that
can only look up one account record at a time, and a operation from a different connector to the Audit system (the Audit operation) that can only
insert one account record at a time.
To best meet the performance-related requirements, what scope or scopes should be used and how should they be used to incorporate the Finance
operation and Audit operation into the retrieveBalances flow?
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
AR
Arlie
11 months ago
D is definitely not efficient for this scenario.
CH
Chantay
11 months ago
Wait, can we really use Async for both? Seems odd.
JA
Jaclyn
12 months ago
C seems too risky, both operations need to be handled carefully.
CE
Celestina
12 months ago
Not sure about that, B could handle errors better.
RE
Rene
1 year ago
I think option A makes the most sense for performance.
CI
Ciara
1 year ago
Wrapping both operations in Async sounds tempting, but I wonder if that would really meet the requirements since they can only handle one record at a time.
VE
Veronika
1 year ago
I feel like Until-Successful could be useful for the Finance operation, but I can't recall if it was the right choice for performance.
AN
Andrew
1 year ago
I think we practiced a question similar to this where we used Async for non-blocking operations. It might apply to the Audit operation.
KR
Krissy
1 year ago
I remember we discussed using Parallel For-Each for operations that need to run simultaneously, but I'm not sure if that's the best fit here.
RO
Ronald
1 year ago
I'm pretty confident I know the right answer here. The Parallel For-Each scope will allow me to process the records from the Finance system in parallel, while the Async scope will let me insert the records into the Audit system asynchronously. That should meet the performance requirements.
JA
Jackie
1 year ago
Okay, I think I have a strategy here. The key is to use scopes that can handle the single-record limitations of the connector operations. I'll start by considering the Parallel For-Each and Async scopes.
LE
Leonida
1 year ago
Hmm, I'm a bit confused about the differences between the Parallel For-Each, Until-Successful, and Async scopes. I'll need to review those in more detail to determine the best approach.
SH
Sherita
1 year ago
This seems like a tricky question. I'll need to think through the different scopes and how they might impact the performance of the two connector operations.
SA
Sabra
2 years ago
Ooh, someone's trying to trick us with these options! I'm going to go with B, it's the only one that really addresses the performance requirements.
AL
Alishia
2 years ago
Yeah, B is the way to go for sure. It's the only one that really makes sense in this scenario.
RO
Rosio
2 years ago
I agree, B seems like the most logical option to incorporate both operations efficiently.
CE
Cecilia
2 years ago
I think B is the best choice too. It handles the performance requirements effectively.
DE
Dewitt
2 years ago
Haha, this question is like a game of 'Choose Your Own Adventure' for Mule developers. I'm going with B - it's the most robust and reliable approach.
FA
Fausto
2 years ago
D is the way to go! Using a For-Each scope will let us process multiple account records at once, reducing the number of individual calls to the Finance and Audit systems.
RA
Rasheeda
2 years ago
C seems like the best option to me. Wrapping both operations in an Async scope will allow them to run concurrently, improving the overall performance of the flow.
CH
Christiane
2 years ago
Yes, Async scope is the way to go for this scenario. It will help optimize the flow performance.
LA
Larue
2 years ago
Async scope definitely seems like the right choice here. It will speed up the process by running the operations concurrently.
AL
Alyce
2 years ago
I agree, using Async scope for both operations is the way to go for better performance.
HE
Herschel
2 years ago
C seems like the best option to me. Wrapping both operations in an Async scope will allow them to run concurrently, improving the overall performance of the flow.
KA
Kati
2 years ago
I think the correct answer is B. The Until-Successful scope will ensure the Finance operation is retried until it succeeds, while the Try-Catch scope will handle any errors that may occur in the Audit operation.
CY
Cyril
2 years ago
The Try-Catch scope will handle any errors that may occur in the Audit operation.
ET
Ethan
2 years ago
The Until-Successful scope will ensure the Finance operation is retried until it succeeds.
EL
Eleonore
2 years ago
I think the correct answer is B.
YV
Yvonne
2 years ago
The Until-Successful scope will ensure the Finance operation is retried until it succeeds, while the Try-Catch scope will handle any errors that may occur in the Audit operation.
LI
Lili
2 years ago
I think the correct answer is B.
EV
Evangelina
2 years ago
I disagree, I believe option B is better as it ensures the Finance operation is retried until successful before moving on to the Audit operation.
GI
Gilma
2 years ago
I think option A is the best choice because it allows for parallel processing of the Finance and Audit operations.