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

Salesforce Exam MuleSoft Integration Architect I Topic 9 Question 15 Discussion

Actual exam question for Salesforce's MuleSoft Integration Architect I exam
Question #: 15
Topic #: 9
[All MuleSoft Integration Architect I Questions]

An organization is designing a Mule application to periodically poll an SFTP location for new files containing sales order records and then process those sales orders. Each sales order must be processed exactly once.

To support this requirement, the Mule application must identify and filter duplicate sales orders on the basis of a unique ID contained in each sales order record and then only send the new sales orders to the downstream system.

What is the most idiomatic (used for its intended purpose) Anypoint connector, validator, or scope that can be configured in the Mule application to filter duplicate sales orders on the basis of the unique ID field contained in each sales order record?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Gracia
6 days ago
The Cache scope seems like a reasonable option to filter duplicate records based on the unique ID field. It would allow us to store and check each record against the cache.
upvoted 0 times
...
Casandra
23 days ago
I'm not sure, but I think A) Configure a Cache scope could also work to filter and store each record by the order ID. What do you guys think?
upvoted 0 times
...
Eugene
27 days ago
I agree with Alberta. Using an Idempotent Message Validator would be the most idiomatic way to filter duplicate sales orders based on the unique ID.
upvoted 0 times
...
Alberta
28 days ago
I think the answer is C) Configure an Idempotent Message Validator component to filter each record by the order ID.
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