1z0-448 Oracle Data Integrator 12cEssentials Questions and Answers

In the ODI Interface palette, choose the more convenient graphic objects to link the involved servers.

You need not draw directly in the data flow all the details about how the different servers involved are connected. ODI automatically designs the flow and how servers are connected.

You need not draw directly in the data flow all the details about how the different servers involved are connected. The code will be the black box generated directly by ODI.

You must draw directly in the data flow all the details about how the different servers involved are connected, and also specify with variables the passwords for connecting to the data contained in the servers.

ODI topology does not allow defining more than one physical schema for a data server; the associated logical schema would be ambiguous.

It is possible to define more than one physical schema associated to the same data server, but it is mandatory to specify a different user to log in.

It is possible to define more than one physical schema associated to the same data server, but you must flag the default physical schema.

It is possible but it is better to avoid doing so because it is more difficult to define a logical schema this way.

This works only for Oracle and Informix.

This works only for Oracle and MySQL.

Create a new generic technology to support it.

Use the out-ofthe box Generic SQL technology.

Variables

Datastores

Knowledge Modules

Reusable Mappings

They contain data model and security information.

They contain security and topology information.

They contain project and topology information.

They contain project and security information.

They update or modify code to be executed, check security, select database servers, and update log files after execution.

They schedule scenarios to be executed, check security, constraints and update log files after execution.

They retrieve code from the execution repository and request database servers, operatingsystems, or scripting engines for execution.

They schedule code from the execution repository and update log files after execution.

You must consolidate your own local metadata repositories. The local metadata must be transmitted via ftp and synchronized with a dedicated proprietary engine, creating a common metadata model for all the developers.

You must consolidate your own local metadata repositories. You have to invoke a dedicated web service to synchronize the metadata by using Oracle Service Bus.

You need not consolidate your own local metadata repositories, because the ODI proprietary metadata server allows all developers to share the common metadata of a specific project.

You need not consolidate yourown local metadata repositories, because ODI uses a centralized relational metadata repository that all the developers share.

It enables developers to execute most ODI operations through a Java program.

It can be used to embed ODI processes into another product.

It is used to load data between Teradata and Oracle.

It must be used by ETL developers to develop ODI processes.