nerdexam
SAS_Institute

A00-260 · Question #12

When using the Table Loader transformation in SAS Data Integration Studio to update an existing table containing indexes or constraints, which statement is true?

The correct answer is B. You can control the removal and/or creation of indexes and constraints in the target table for all. Option B is correct because the Table Loader transformation in SAS Data Integration Studio provides full control over index and constraint management - both removal and creation - regardless of which load style is selected (Replace, Append, Update/Insert, etc.). This…

Create and work with metadata for SAS Data Integration Studio

Question

When using the Table Loader transformation in SAS Data Integration Studio to update an existing table containing indexes or constraints, which statement is true?

Options

  • AYou can control the removal and/or creation of indexes and constraints in the target table only if
  • BYou can control the removal and/or creation of indexes and constraints in the target table for all
  • CIf using the Append to Existing load style, indexes and constraints can be added but not removed.
  • DFor the Update/Insert load style it is possible to remove indexes not required for the Update/Insert

How the community answered

(29 responses)
  • A
    3% (1)
  • B
    79% (23)
  • C
    14% (4)
  • D
    3% (1)

Explanation

Option B is correct because the Table Loader transformation in SAS Data Integration Studio provides full control over index and constraint management - both removal and creation - regardless of which load style is selected (Replace, Append, Update/Insert, etc.). This flexibility is a deliberate design feature to ensure target table integrity across all loading scenarios.

Option A is a trap: the phrase "only if" implies a conditional restriction that doesn't exist - you have this control unconditionally across all load styles. Option C incorrectly claims that the Append load style restricts you to adding but not removing indexes and constraints, which misrepresents the tool's capabilities. Option D misleads by suggesting the Update/Insert style has a unique or special limitation on index removal, implying other styles don't share this control - but in reality, the control is universal.

Memory tip: Think "B for Blanket control" - option B gives you blanket (all load styles) control over both adding and removing indexes and constraints, with no asterisks or exceptions.

Topics

#Table Loader transformation#Indexes and constraints#Load styles#Target table metadata

Community Discussion

No community discussion yet for this question.

Full A00-260 Practice