Salesforce Certified Platform Integration Architect free question 9 / 10 · Domain 5: Build Solution
A Bulk API job reports its batch as Completed, and the integration marks the load as successful without reading the results. A few days later, users find missing records. What does the guide say about the batch state and how to find failures?
- A Completed batch has no failed records, given that a failed record changes the batch to a Failed state for the whole job
- A Completed batch rolls back its successful records when a record fails, so the integration should resubmit the whole file
- A Completed batch can still contain failed records, given that the batch state does not show them, so read the Success field
- A Completed batch lists its failures in the job’s state description, so the integration needs to check the job state description
Show the answer and explanation
Answer: C
Why this is correct
The guide explains that a batch can have a Completed state even if some or all of the records failed. If a subset failed, the successful records aren’t rolled back, and even when a batch is in a Failed state or the job is aborted, some records could have completed. So when you get the batch results, it’s important to look at the Success field for each result row, and the Error column explains failures.
Why the other options are wrong
"A Completed batch has no failed records, given that a failed record changes the batch to a Failed state for the whole job" … The guide says a batch can be Completed even if some or all records failed. Successful records are not rolled back.
"A Completed batch rolls back its successful records when a record fails, so the integration should resubmit the whole file" … If a subset of records failed, the successful records aren’t rolled back. Resubmitting the whole file would duplicate them.
"A Completed batch lists its failures in the job’s state description, so the integration needs to check the job state description" … The guide says to get the batch results, track the record number for each result row, and check the Success field and Error column.
Where people trip
Job and batch states describe processing, not data quality. Always parse the result rows, in order, and log the failures.