Select the valid reasons for using SAS Data Integration Studio's Table Loader transformation. (Choose two.)

Question

Options

• ACreate and replace permanent tables.
• BMaintain access privileges to permanent tables.
• CApply and maintain constraints on permanent tables.
• DDelete and remove permanent tables.

• A
  8% (5)
• B
  3% (2)
• C
  89% (56)

Explanation

Options C and D are correct because the Table Loader transformation in SAS Data Integration Studio is specifically designed to manage the structure and lifecycle of permanent tables - it provides built-in options to apply and maintain integrity constraints (such as PRIMARY KEY, FOREIGN KEY, NOT NULL, and CHECK constraints), and it also supports deleting rows from and physically removing permanent tables as part of its load operations.

Option A is a distractor because creating or replacing tables is handled through table registration in the SAS metadata repository or DDL-type transformations, not the Table Loader itself. Option B is incorrect because managing access privileges (GRANT/REVOKE) is a database security concern handled outside of SAS DI Studio's Table Loader - it falls under DBA responsibilities or SAS metadata security settings.

Memory tip: Think of the Table Loader as a "table manager," not just a "data pusher." The two things it manages beyond loading rows are Constraints (C) and Cleanup/Deletion (D) - both relate to controlling the table's rules and existence, not its permissions or initial creation.

No community discussion yet for this question.