SAP Certified Technology Associate - OS/DB Migration for SAP NetWeaver 7.4 - C_TADM70_74 Free Exam Questions

A. If the R3LOAD export was done by someone else and you are not responsible for the import.

B. All are true

C. In case of import errors, because of dump corruptions, the export logs should be examined for
troubleshooting

D. The R3LOAD export process is not sensitive

A. Standard objects in the target database

B. Non-standard objects in the target database

A. Target system

B. Source system

A. Netweaver version specific

B. Efficient data compression

C. Restart capable for data export and import

D. Dump format is dependent of database and operating system

E. Table splitting (since 7.02)

A. Where files systems can be shared between source and target system

B. Where source and target system donot have a network connection, or the existing connection is
too slow for a file transfer

A. SAPINST calls the software Deployment manager (SDM) to reinstall (deploy) its files system
components
Red SDM repository (list of deployed components)
Put file system components into the SDMKIT.JAR file

B. All are false

C. SAPINST starts SAPCAR to archive application specific data stored in the file system
As a prerequisite, the application must be known by SAPINST various*.SAR files can be created.

D. SAPINST calls the software Deployment manager (SDM) to reinstall (deploy) its files system
Components including the SDM respository from the SDMKIT.JAR

A. The existence of a matching export *.STA file identifies a restart situation, otherwise the export
starts from scratch.

B. If no job file is specified, the complete database will be exported by default

C. If JPKGCTL was used meta data and table data were put into separate dump files.

D. The existence of a matching import *.STA file identifies a restart situation, otherwise the import
starts from the first data dump file entry.

A. The export client mode applies, where R3SETUP/SAPINST performs the database export, and
MIGMON is used for the import.

B. Even if MIGMON was not used to perform the export, the import can still benefit from the
advance
MIGMON R3LOAD control features

C. Even the number of export and import process can be different but un the case of socket usage,
the number of export and import processes is the same.

D. The client MIGMON is used to transfer the files to the target host and to signal the importing
MIGMON, that a package is ready to load.