Q. If the preceding job was run on a batch with a 100 rows, each item was read and passed through the processor, and it found 10 items invalid (it returned null 10 times), the value for the filter_count column would be:-

View solution

Q. Transaction capabilities are built on top of the first class support already provided by the core Spring framework.

View solution

Q. Spring core framework provides first-class support for transactions.

View solution

Q. The batch.xml file establishes a:-

View solution

Q. Spring Batch will, by default, try to pluck the:-

View solution

Q. Spring Batch excels in the robustness it surfaces as simple configuration options for the edge and failure cases.

View solution

Q. Element to configure this for the step:-

View solution

Q. You want to work with a resource that may fail when you try to read from or write to it.

View solution

Q. Some invocations will fail but may be retried with some likelihood of success in a transactional scenario.

View solution

Q. You can leverage Spring Batch support for retries and recovery in your own code.

View solution

Q. The template that (much like its various other Template cousins) isolates your logic from the nuances of retries and instead enables you to write the code as though you were only going to attempt it once.

View solution

Q. The RetryTemplate supports many use cases, with convenient APIs to wrap.

View solution

Q. The RetryTemplate itself is configured in the Spring context, although it’s trivial to create in code.

View solution

Q. One of the more useful settings for the RetryTemplate is the :-

View solution

Q. You want to control how steps are executed, perhaps to eliminate a needless waste of time by:-

View solution

Q. Typical jobs of almost any complexity will have multiple steps, however.

View solution

Q. There’s nothing to prevent you from having many steps within the flow elements.

View solution

Q. Spring Batch provides a mechanism to offload processing to another process.

View solution

Q. Pattern which refers to the arrangement of multiple JMS clients all consuming the same queue messages.

View solution

Q. Spring Batch ships with only handler, which executes steps in multiple threads using a TaskExecutor strategy.

View solution