000-349 Question #3: Real Exam Question with Answer & Explanation

The correct answer is D. FetchAs= Burst, Scope=Map, OnSuccess=Delete, OnFailure=Rollback. For a 2GB file where all records must be valid before any data is committed, FetchAs=Burst prevents memory exhaustion while Scope=Map ensures the entire map is treated as a single transaction.

Question

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 settings?

Options

AFetchAs= Integral, Scope=Map, OnSuccess=Delete, OnFailure=Rollback
BFetchAs= Burst, Scope=Burst, OnSuccess=Delete, OnFailure=Rollback
CFetchAs= Integral, Scope=Card, OnSuccess=Delete, OnFailure=Rollback
DFetchAs= Burst, Scope=Map, OnSuccess=Delete, OnFailure=Rollback

Explanation

For a 2GB file where all records must be valid before any data is committed, FetchAs=Burst prevents memory exhaustion while Scope=Map ensures the entire map is treated as a single transaction.

Common mistakes.

A. 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.
B. 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.
C. 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.

Concept tested. Card settings for large file processing with map-level transactional validation

Reference. https://www.ibm.com/docs/en/wtx/8.4.1?topic=cards-card-settings-fetchas-scope

Community Discussion

No community discussion yet for this question.

Full 000-349 Practice