Examine the following impdp command to import a database over the network from a pre-12c Oracle database (source): 
Which three are prerequisites for successful execution of the command?
A.
The import operation must be performed by a user on the target database with the
DATAPUMP_IMP_FULL_DATABASE role, and the database link must connect to a user on the
source database with the DATAPUMP_EXD_FULL_DATABASE role.
B.
All the user-defined tablespaces must be in read-only mode on the source database.
C.
The export dump file must be created before starting the import on the target database.
D.
The source and target database must be running on the same platform with the same
endianness.
E.
The path of data files on the target database must be the same as that on the source database.
F.
The impdp operation must be performed by the same user that performed the expdp operation.
Explanation:
A, Not F :The DATAPUMP_EXP_FULL_DATABASE and
DATAPUMP_IMP_FULL_DATABASE roles allow privileged users to take full advantage of the
API. The Data Pump API will use these roles to determine whether privileged application roles
should be assigned to the processes comprising the job.
Note:
* The Data Pump Import utility is invoked using the impdp command.
Incorrect:
Not D, Not E: The source and target databases can have different hardware, operating systems,character sets, and time zones.
It’s A,B,E
C is wrong because you’re using a network expdp/impdp
D is wrong because you can convert endianness with rman, and multiple platforms transport is possible.
E is right, because else the clause would be: transport_datafiles=’source’,’destination’, for all datafiles.
Here are 3 datafiles, so this could never be the issue.
ABD
Agree (export dump even is not mentioned in the script)
AB ???
### Not D
If the source platform and the target platform are of different endianness, then you must convert the data being transported so that it is in the format of the target platform. You can use the DBMS_FILE_TRANSFER package or the RMAN CONVERT command to convert the data. See Oracle Database Administrator’s Guide for more information about using either of these options.
https://docs.oracle.com/database/121/SUTIL/dp_import.htm#SUTIL893
### Not E
Test:
http://oracleinaction.com/12c-transport-database-network/
### Not F
expdp is not needed.
Hi Andrey
impdp system/oracle full=y network_link=orcl_link transportable=always transport_datafiles=’/u01/app/oracle/oradata/dest/users01_orcl.dbf’,’/u01/app/oracle/oradata/dest/example01_orcl.dbf’ version=12 logfile=import.log
As Ledeboer, Jeroen said if the path is not same you should define target path as in the example in your link I think you missed it or Am I wrong ?
It will be ABD. C does not make sense since it is network link impdp which itself creates export dump on the fly and does not need an already present export dump file.
To transport the database over the network use import with the NETWORK_LINK parameter
The import is performed using the database link and there is “NO DUMP FILE INVOLVED”
This text pasted from oracle university book.
So the correct answer is ABD
sorry A , B and E
not D
ABD E is wrong because you copy the tablespace datafile from source to target before running the impdp command. In the impede command you use the structure of the target db to define the place of the datafiles. Therefore no need that the path is the same.
A B D,
A and B are obvious, but D because you transfer them over network, there aren`t such think as implicity endian conversion, if you want to do this you have to transfer them by copying them to remote host and then made conversion using RMAN
A B D,
The presence of the TRANSPORT_DATAFILES parameter tells import that it is a transportable-mode import and where to get the actual data.
https://docs.oracle.com/database/121/SUTIL/GUID-4F26914E-28D2-428C-9F20-256A3C861068.htm#GUID-4F26914E-28D2-428C-9F20-256A3C861068__CIHCAHFB
So TRANSPORT_DATAFILES parameter defines a new datafile names(rename) on the target.
ABD