What the published objective requires
- Select For Each or Batch from workload behavior
- Filter and route batch records
- Persist watermarks and cross-event state
Domain 7 of 12 · 10% of the official blueprint
Processing Records practice lesson
Choose between in-event iteration, batch processing, polling and persistent state for Northstar workloads.
The misconception to eliminate
Selecting Batch merely because a payload is an array, or Object Store whenever any data must persist.
Practice allocation: 6 of 60 questions in our whole-question mock blueprint.
Decision rules
Retrieve these without looking before attempting the question.
Rule 1
For Each iterates a collection in the current flow; it is not a persistent batch job.
Rule 2
Batch splits data into records, runs staged processing and tracks record-level outcomes.
Rule 3
A watermark prevents a polling source from rereading already processed rows.
Rule 4
Use Object Store for simple key-value state, not as a transactional database replacement.
Worked Northstar scenario
Scenario
Nightly import contains 100,000 acknowledgements and five percent may fail independently.
Reasoning
Use Batch so records can be filtered, processed in steps and reported individually. A synchronous For Each would tie the entire workload to one flow execution and coarse failure boundary.
Free practice question
A collection has 12 items and all must be processed synchronously in order. Which scope is the simplest fit?
- Batch Job
- For Each
- APIkit Router
- Scheduler
Reveal answer and reasoning
Answer: B. For Each is appropriate for a small in-event sequential iteration when persistent batch semantics are unnecessary.
The complete program contains five guided drills for this domain, an 80% mastery gate, saved progress and a separate 60-question timed mock.
Get Domain MasteryHands-on proof preview
Design the nightly import
Create a record-processing plan before implementation.
- Define the input record and correlation key.
- Separate validation and ERP-update batch steps.
- Add an accept expression for valid supplier codes.
- Verify failed-record counts and successful updates are both visible at completion.
Evidence to keep: A two-step batch design with an accept expression, failure policy and reconciliation totals.
Primary sources
Questions about this domain
How much of the MuleSoft Developer exam is Processing Records?
Salesforce publishes a weight of 10% for this domain. In a 60-question practice allocation, that is represented here by 6 questions.
Is this Processing Records question from the real exam?
No. It is original independent practice material written only from public exam objectives and product documentation.