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

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.

ODI Runtime Agent

ODI Standalone Agent

ODI JEE Agent

ODI Colocated Standalone Agent

They can have generic input and output signatures.

They contain both a Logical and Physical Mapping design.

They can be used within regular Mappings.

They can be executed directly.

They can be shared across projects.

extracting source data to flat files

triggers

Oracle GoldenGate

before-and-after database image comparison

Create one Logical Schema per Physical Schema.

Create one Logical Schema per Physical Schema that stores the same type of data.

Create one Logical Schema per Data Server.

Create one Logical Schema per Context.

It is only possible to see code at the Session level.

It is only possible to view code at the Task level.

Depending on the audit level declared when running the execution, some of the generated code at the step level can be viewed.

All generated code can be viewed together at the step level, with a complete list of executed code.

Oracle BPEL Process Manager

Oracle GoldenGate

ODI Console

Oracle WebLogic Server

ODI uses its own transformation engine to process data in a Hadoop cluster.

ODI performs data transformations inside a Hadoop cluster.

ODI must perform data transformations outside Hadoop in an Oracle database.

ODI allows moving data in and out of a Hadoop cluster.