Examine this set of commands to perform data pump export and import operations: On the source database: $> expdp sh/sh DIRECTORY=dpdir DUMPFILE=sale1.dmp VIEWS_AS_TABLE=sales_q1 On the target…

Question

Options

• AThis impdp operation creates the view as a table and populates it with data from the export dump
• BThe exdp operation exports data that satisfies the conditions of the defining query used when the
• CMetadata for dependent objects required to create the SALES_Q1 view is exported.
• DAll rows from the dependent objects that are required are exported along with the metadata to
• EThe impdp operation creates the view and the dependent object.

• A
  83% (25)
• C
  13% (4)
• D
  3% (1)

Explanation

The VIEWS_AS_TABLE parameter instructs Data Pump to treat a view as a table during export and import. During export (B), only the rows that satisfy the view's defining SELECT query are captured - not all rows from the underlying base tables. On import (A), a new table is created using the view's name and populated with those exported rows; the view itself is not recreated. Choice E is correct because the import re-creates the data structure as a table on the target system, making the data available even if the underlying base tables do not exist there. Choice C is incorrect: VIEWS_AS_TABLE does not export DDL metadata for dependent base tables - the whole point is to bypass dependency on those tables. Choice D is incorrect because only the rows returned by the view query are exported, not every row from every underlying table.

No community discussion yet for this question.