If the application developer wants to read a 2GB file that contains two million records of 1KB each and ensure that no data is processed unless all the input data is valid. What are the correct card…

FetchAs=Integral attempts to load the entire 2GB file into memory at once, which is impractical for a file of this size and risks out-of-memory errors.

Scope=Burst limits the transaction boundary to each individual burst, so successfully processed bursts could be committed even if a later burst contains invalid records, violating the all-or-nothing requirement.

FetchAs=Integral would load the entire 2GB file into memory causing resource exhaustion, and Scope=Card limits rollback granularity to individual cards rather than the full map execution.

FetchAs=Burst reads the 2GB input file in manageable chunks rather than loading it entirely into memory at once, preventing the out-of-memory failures that FetchAs=Integral would cause with a file of this size. Scope=Map wraps the entire map execution in one transaction boundary, so the OnFailure=Rollback applies across all records - guaranteeing that no output is committed if any single record fails validation. Together these settings satisfy both the memory efficiency requirement and the all-or-nothing validation constraint.