1Z0-062 · Question #308
Which statement is true about using the Export/Import method for migrating data when upgrading to Oracle Database 12c?
The correct answer is D. It allows migration of a database directly over network links.. When migrating data using Oracle Data Pump Export/Import, it supports direct data transfer over network links between source and target databases without requiring intermediate dump files.
Question
Which statement is true about using the Export/Import method for migrating data when upgrading to Oracle Database 12c?
Options
- AIt automatically restarts a Data Pump Export or Import job after a failure is connected and the job
- BIt can be used to migrate a database only if the source and target databases are hosted on the same
- CIt can be used to migrate a database only if the source database does not have any tablespace in read-
- DIt allows migration of a database directly over network links.
How the community answered
(41 responses)- A2% (1)
- B5% (2)
- C2% (1)
- D90% (37)
Why each option
When migrating data using Oracle Data Pump Export/Import, it supports direct data transfer over network links between source and target databases without requiring intermediate dump files.
While Data Pump jobs can be restarted after a failure, this is a manual process requiring an administrator to attach to the job, not an automatic restart.
Export/Import is a flexible method used to migrate databases between different servers, operating systems, and even different database versions, so they do not need to be hosted on the same system.
Data Pump Export can successfully export data from tablespaces that are in read-only mode, as the export process only reads data and does not require write access to the source data files.
Oracle Data Pump, the modern Export/Import utility, supports network mode, enabling the migration of a database directly across network links from a source database to a target database using a database link.
Concept tested: Oracle Data Pump network mode migration
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/arpls/DBMS_DATAPUMP.html#GUID-B7F9412F-46C9-4C4A-B66A-915904D1B078
Topics
Community Discussion
5D is correct because Oracle Data Pump Export/Import supports network mode via the NETWORK_LINK parameter, allowing you to pull data directly from a source database over a database link without staging dump files on disk first. The distractors each impose restrictions (same host, no read-only tablespaces) that simply do not exist as hard requirements for the Export/Import migration method.
Think of Data Pump like a garden hose connecting two tanks, where you can just run the hose directly from the old tank to the new one without filling up any buckets in between. That direct hose is the NETWORK_LINK parameter, and it is exactly what option D is describing, so D is your answer. A lot of people get pulled toward A because Data Pump absolutely does let you attach to a stopped job and restart it, that part is true, but the sentence is garbled in a way that should make you suspicious, and more importantly it is not a statement about migration capability specifically. B and C are both flat wrong, the tool has no requirement that source and target share a host or that tablespaces be in a particular state.
Solid breakdown, though worth flagging for students that NETWORK_LINK requires a database link pre-created on the target pointing back to the source, so it is not quite a plug-and-play hose, there is a CREATE DATABASE LINK step that shows up in the exam as its own gotcha.
Saw this exact flavor of question on my exam and nearly second-guessed myself on D because the wording felt too clean, but then I remembered that Data Pump impdp with NETWORK_LINK pulls data straight across a database link with no dump file sitting in the middle, which is the whole point of the feature. The distractors are garbage, A describes a real behavior but it is about job restart not migration method, B and C are just made-up restrictions that Oracle never imposed.
Solid instinct on D, and worth adding for anyone who blanks on exam day: the database link specified in NETWORK_LINK must exist on the target database and point back to the source, not the other way around, which is the detail that trips people up when they try to recreate this in a lab.