1Z0-052 · Question #212
User SCOTT wants to export his objects using Oracle Data Pump and executes the following command: $ expdp scott/tiger directory = EXPORT_DIR dumpfile = scott.dmp include = table include = view:"like…
The correct answer is C. Oracle Data Pump would export the table data and the view definitions where the view name. The expdp command exports row data from all tables and identifies views matching '%DEPARTMENTS%' using an object filter, with 'content=DATA_ONLY' restricting the export to data rows rather than DDL definitions.
Question
User SCOTT wants to export his objects using Oracle Data Pump and executes the following command:
$ expdp scott/tiger directory = EXPORT_DIR dumpfile = scott.dmp include = table include = view:"like '%DEPARTMENTS%'" content = DATA_ONLY Which task would the command accomplish?
Options
- AOracle Data Pump would export only the data of all of the tables and views.
- BOracle Data Pump would export all of the table structures along with data and all the views.
- COracle Data Pump would export the table data and the view definitions where the view name
- DOracle Data Pump would export the table data and the view definitions with data where view name
- EOracle Data Pump would export all of the table structures and the view definitions with data where
How the community answered
(32 responses)- B9% (3)
- C81% (26)
- D6% (2)
- E3% (1)
Why each option
The expdp command exports row data from all tables and identifies views matching '%DEPARTMENTS%' using an object filter, with 'content=DATA_ONLY' restricting the export to data rows rather than DDL definitions.
This option incorrectly claims that data from both tables and views is exported; views are logical definitions with no stored rows, so Data Pump cannot export row-level data from a view object.
This option incorrectly states that table structures (DDL such as CREATE TABLE statements) are exported; the 'content=DATA_ONLY' parameter explicitly suppresses all object definitions and metadata from the export.
The 'include=table' parameter selects all table objects for the export job, while 'include=view:"like \'%DEPARTMENTS%\'"' uses an object filter expression to include only views whose names match the pattern. The 'content=DATA_ONLY' parameter tells Data Pump to unload only the actual table row data and excludes object metadata, so tables contribute their data while the view filter identifies which view objects are in scope.
This option implies that view row data is also included in the export; because views do not store rows independently, there is no view-level data for Data Pump to extract regardless of the content setting.
This option incorrectly claims table structures are exported alongside view definitions with data; 'content=DATA_ONLY' prevents any DDL or structural metadata from being written to the dump file.
Concept tested: Oracle Data Pump expdp include filter and DATA_ONLY content mode
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-export-utility.html
Topics
Community Discussion
5
Ingrid P.Dec 6, 2025C is correct. The command uses CONTENT=DATA_ONLY, which means only row data is exported without DDL, and the INCLUDE parameters tell Data Pump to scope the export to all tables (data only) and to views matching the name pattern '%DEPARTMENTS%' (definitions only, since views have no data of their own), so the net result is table row data plus the qualifying view definitions.
Dragan P.Dec 6, 2025CONTENT=DATA_ONLY suppresses all metadata including DDL, so that INCLUDE=VIEW filter is dead weight in this export, the view definitions never land in the dump file, and if the answer key says they do, the answer key is wrong.
Carlos M.Dec 6, 2025C is the right call here. The command has two separate INCLUDE filters: one for TABLE with no filter (so it grabs all tables) and one for VIEW with a LIKE condition limiting it to views whose names contain DEPARTMENTS. The key thing that trips people up is CONTENT=DATA_ONLY, which controls the data side but does not suppress object definitions from being exported when you use INCLUDE, so the view DDL still goes into the dump. What DATA_ONLY actually means is that for the tables, you get rows but no CREATE TABLE DDL, and the view definitions come along because views themselves have no "data" to strip, just their query definition.
Luis F.Jan 6, 2026Option D is tempting because it mentions "view definitions with data" and you might think DATA_ONLY applies to views too, but views don't store data so that's a trap. The command exports all table data (no structure because of DATA_ONLY) plus the view definitions where the view name matches the LIKE filter, which is exactly what C says.
Carlos M.Jan 7, 2026Right, and the easier way to remember it on exam day is that DATA_ONLY only suppresses DDL for objects that actually have rows, so views always come along as definitions regardless of that flag.