A00-260 · Question #30
How can you test the interaction of the options of a SAS Data Integration Studio Generated transformation?
The correct answer is D. The options can be tested at any time after adding them to the transformation with the Test. Option D is correct because SAS Data Integration Studio's Generated transformation wizard includes a Test Prompt button that becomes available immediately after an option is added - there is no requirement to complete, finalize, or deploy the transformation first, making…
Question
How can you test the interaction of the options of a SAS Data Integration Studio Generated transformation?
Options
- AThe transformation has to be used within a job to interactively test the options with the Test
- BThe options can be tested after finalizing and saving the transformation with the Test Prompt item
- CThe options can be tested only after adding all options that are assigned to the source code with
- DThe options can be tested at any time after adding them to the transformation with the Test
How the community answered
(18 responses)- A6% (1)
- C6% (1)
- D89% (16)
Explanation
Option D is correct because SAS Data Integration Studio's Generated transformation wizard includes a Test Prompt button that becomes available immediately after an option is added - there is no requirement to complete, finalize, or deploy the transformation first, making iterative testing during development straightforward.
Why the distractors fail:
- A is wrong because you do not need to embed the transformation inside a job to test its options; testing is available directly within the transformation editor itself.
- B is wrong because finalization and saving are not prerequisites - you can test options mid-development without committing to a saved state.
- C is wrong because it falsely implies you must add all options before testing any; you can test each option individually as you build them.
Memory tip: Associate option D with the word "any" - "at any time" signals maximum flexibility. SAS DI Studio is designed for iterative development, so testing is never gated behind a completion step.
Topics
Community Discussion
No community discussion yet for this question.