MuleSoft Certified Integration Architect – Level 1 — Question 93

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?

Answer options

• A. Configure a Cache scope to filter and store each record from the received file by the order ID
• B. Configure a Database connector to filter and store each record by the order ID
• C. Configure an Idempotent Message Validator component to filter each record by the order ID
• D. Configure a watermark In an On New or Updated File event source to filter unique records by the order ID

Correct answer: C

Explanation

The correct answer is C because an Idempotent Message Validator is specifically designed to ensure that messages with the same unique identifier are not processed more than once, which aligns perfectly with the requirement of processing each sales order exactly once. Options A and B involve caching or database storage, which do not inherently prevent duplicate processing. Option D is not suitable as watermarks are typically used for tracking states rather than directly filtering duplicates based on unique IDs.