フリー問題

問題文

A developer is assembling the nightly retail load and is also packaging one stage of it so that four other mappings can each drop the same stage into their own pipeline. Two points come up. One object inside the packaged stage is refused unless it has been defined once and shared. Elsewhere in the load two objects sit side by side, and the team needs to know which of them hands on the number of rows, the commit points and the flags on each row exactly as it found them. Which pairing fits?

選択肢

1. Only the reusable form of the Sequence Generator transformation is allowed inside the packaged stage, and the number of rows, the commit points and the flags on each row all come out untouched from the External Procedure transformation.
2. Only the reusable form of the Sequence Generator transformation is allowed inside the packaged stage, and the number of rows, the commit points and the flags on each row all come out untouched from the Transaction Control transformation.
3. Only the reusable form of the Source Qualifier transformation is allowed inside the packaged stage, and the number of rows, the commit points and the flags on each row all come out untouched from the Transaction Control transformation.
4. Only the reusable form of the Source Qualifier transformation is allowed inside the packaged stage, and the number of rows, the commit points and the flags on each row all come out untouched from the External Procedure transformation.