1Z0-448 ODI (No cloud)

From the source database into flat files that are then loaded into the target database

Directly from the source database to the target database

From the source database onto the server running the Agent and then into the target database

From the source database into the machine running ODI Studio and then into the target database

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 your own local metadata repositories, because ODI uses a centralized
relational metadata repository that all the developers share.

Use a dedicated schema such as ODI_STAGING

Use TEMP

Use the same schema as the Data Schema

Use SYSTEM

Create a single Mapping with two Physical Designs: one for the initial load and one for the
incremental updates.

Create a single Mapping with a single Physical Design and modify it appropriately when an initial load is required or when an incremental update is required.

Create two Mappings: one for the initial load and one for the incremental updates. Duplicate the
transformation logic.

Create a single Mapping and use variables in the Logical Design to do an initial load when required or an incremental update otherwise.

By using Opatch

By using the import/export utilities

By using ODI Studio

By using Upgrade Assistant

Right–click the step in Package Editor and select the No Logging menu item.

Modify Operator Navigator settings to disable that step from being displayed.

In Package Editor, click the step, go to the Advanced tab, and set Log Steps in the journal to Never.

Periodically schedule a scenario that uses OdiPurgeLog to remove that step from the ODI logs

Create a custom KM to handle this by using ODI variables defined at the Topology level to create
unique temporary object names.

Use variables in the Logical Design of the Mapping to create unique temporary object names.

Create a custom Knowledge Module (KM) to handle this by using ODI variables to create unique
temporary object names.

Select the Use Unique Temporary Object Names check box at the Physical Design level.

ERR$

ERROR$

ODI_ERR$

E$

The project must be explicitly mapped within an ODI mapping.

A customize knowledge module is needed.

An ODI procedure must be associated with it.

It can be defined for every technology listed in the topology.

All distinct entries are processed.

Only the latest entry is processed based on the JRN_DATE field.

Only the first entry is processed based on the JRN_DATE field.

A PK violation occurs due to the duplicated entries and the entries are inserted in the E$ table.

numeric

alphanumeric

date

text

Data transformation must be distributed across several scalable nodes.

It is mandatory to have an intermediate server.

It is better to load data directly from sources into a data warehouse server.

It is mandatory to collect data directly from sources to a data warehouse server by using real time replication processes.

OdiWaitForData

OdiWaitForCDCData

OdiWaitForLogData

OdiWaitForTable

Oracle BPEL Process Manager

Oracle GoldenGate

ODI Console

Oracle WebLogic Server

transform only

load and transform

extract and load

extract and transform

Go to Security, assign the NG DESIGNER profile to user “A.” Next, drag project “P1” to user “A” and finally setView privilegesto Active for the Mapping objects.

Go to Security, assign the DESIGNER profile to user “A.” Next, drag project “P1” to user “A” and finally set View privileges to Active for the Mapping objects.

Go to Security, assign the NG DESIGNER profile to user “A.” Next, drag project “P1” to user “A” and finally set View privileges to Active for the Project, Folder, and Mapping objects.

Go to Security, assign the DESIGNER profile to user “A.” Next, drag project “P1” to user “A” and finally set View privileges to Active for the Project, Folder, and Mapping objects.

Open the model, go to the Journalizing tab, and modify the order there.

Right–click Datastore, select Changed Data Capture, and then select Order.

Open the model, go to the Journalized tables tab, and modify the order there.

Open the data stores, go to the Journalizing tab, and modify the order there.

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–of the box Generic SQL technology.

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 option is inherited from reverse engineering.

This option is always available.

You can never make this choice.

This option may be available only if the underlying technology supports it.

Create a Data Server by using the File technology and specify the various record formats while reverse engineering the file.

Create a Data Server by using the XML technology, create and nXSD file by using the Native Format Builder, and then reverse engineer it in a Model.

Create a Data Server by using the File technology, create and nXSD file by using the Native Format Builder, and then reverse engineer it in a Model.

Create a Data Server by using the Complex File technology, create and XSD file by using the Native Format Builder, and then reverse engineer it in a Model.

OdiOutFile

OdiFileCopy

OdiFileMove

OdiInFile

ODI Runtime Agent

ODI Standalone Agent

ODI JEE Agent

ODI Colocated Standalone Agent

Open the Task in Operator, go to Code, click Edit, use Pre–execution Code to edit the code, and save it.

It is not possible to modify the code once it has been generated.

Open the Step in Operator, edit the code, and save it.

Open the Task in Operator, go to Code, click Query/Execution Plan to edit the code, and save it.

Go to the Physical tab, select the Fixed Design check box of the Physical Mapping Design.

Go to the Physical tab, select the Is Frozen check box of the Physical Mapping Design.

Go to the Physical tab, select the Read–only check box of the Physical Mapping Design.

Go to the Physical tab, deselect the Modify check box of the Physical Mapping Design.

You can add a primary key even if it does not physically exist on the related database catalog, by adding constraints on the data store.

You can add a primary key even if it does not physically exist on the related database catalog, by adding constraints to the data store diagram.

You cannot add a primary key if it does not physically exist on the related database catalog. You can flag only non–null conditions to be checked.

You cannot add a primary key if it does not physically exist on the related database catalog. You can reverse engineer only the existing constraints.

Consistent set journalizing runs faster than simple journalizing.

Consistent set journalizing always uses Oracle Golden Gate.

Consistent set journalizing treats each data store individually.

Consistent set journalizing provides a guarantee of consistency of the captured changes.

odiMasterRepository

MasterRepository

odimasterrepository

ODIMasterRepository

Create a procedure and add two tasks.

Create a Knowledge Module.

Create a counter variable.

Create a procedure

Regenerate the existing scenario

Nothing, the existing scenario will automatically be updated.

Generate a new scenario and create a new schedule.

Generate a new scenario and attach the previous scenario’s schedule to it

Use OdiPingAgent in a package to ping AGT agent.

In Topology, test the connections to servers A and B by using the AGT agent.

In Topology, test the connections to the AGT agent.

In Topology, test the connections to servers A and B by using Local (No Agent).

Create a variable, use odiRef.getPrevStepLog () in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

Create a variable, use odiRef.getPrevInfo () in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

Create a variable, use odiRef.getStep () in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

Create a variable, use odiRef.getPrevStepStatus () in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

Add a new subscriber and edit the default Journalizing filter in your Mappings.

Drop the journal, add a new subscriber, start the journal, and edit the default Journalizing filter in your Mappings.

Drop the journal, remove existing subscribers, add a new subscriber, start the journal, and edit the default Journalizing filter in your Mappings.

Add a new subscriber, start the journal, and remove the default Journalizing filter in your Mappings.

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.

Add data stores to the package, set Datastores steps to Journalizing Datastore, and select the Extend Window and Lock Subscriber check boxes.

Add data stores to the package, set Datastores steps to Journalizing Datastore, and select the Unlock Subscriber and Purge Journal check boxes.

Add a model to the package, set the Model step to Journalizing Model, and select the Extend Window and Lock Subscriber check boxes.

Add a sub model to the package, set the Sub–model step to Journalizing Sub–model, and select the Extend Window and Lock Subscriber check boxes.

Start a Mapping in Debug mode and use breakpoints and the Get Data feature to query the data contained in the Staging tables.

Modify a Knowledge Module to dump the Staging tables’ data into log files for review.

Use variables in a Package to query the Staging tables and evaluate the variable values.

Reverse engineer the Staging tables in a Mode land review the data contained in it.

the schema hosting the Work repository

the schema hosting the Work schema of the default schema defined for your source data server

the schema hosting the Staging Area

SYS

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.

The Knowledge Module must be customized because business rules and the physical implementation are strictly interlayed in ODI.

The Knowledge Module must be customized only for aggregation functions.

The Knowledge Module need not be customized because aggregation code is generated automatically by ODI according to the Mapping logic.

The Knowledge Module need not be customized, but a variable must be used in the aggregate expression to generate the correct sum.

Only an Integration Knowledge Module single–technology is required.

Only an Integration Knowledge Module multitechnology is required.

A loading Knowledge Module multitechnology and an Integration Knowledge Module single– technology are required.

Both a Loading Knowledge Module multitechnology and an Integration Knowledge Module multitechnology are required.

It is not possible to enforce constraints on some technologies such as flat files and Java Messaging Service (JMS) queries.

It is not possible to enforce constraints on any technology.

It is only possible to forward–engineer it to the flat file definition.

It is possible to enforce a primary key on a flat file by using a CKM; however, you have to save it as a fixed file.

./agent.sh –NAME=OracleDIAgent1 –PORT=20910

./agent.sh –NAME=OracleDIAgent1

./startComponent.sh OracleDIAgent1

./startComponent.sh OracleDIAgent1 –PORT=20910

Add a sub–model to a package, set the Sub–model step to Journalizing Sub–model, and select the Extend Window and Lock Subscriber check boxes.

Add an OdiSendMail step to a knowledge module.

Duplicate the OdiSendMail step into multiple packages.

Create a procedure with a step that uses OdiSendMail and add this procedure into multiple packages.

It is possible to set the execution location on source, staging area, or target.

All transformations are executed on the staging area.

Only the source and target servers can be used to execute expressions.

All expressions are executed on the source area.

on the Coherence Server

on the Administration Server

on the Node Manager

on the Managed Server

You need not deploy the generated code manually in a source or target server. ODI Agent coordinates the execution of commands prepared for the job, and executes them on the correct server.

You must deploy the generated code manually in a source or target server. You must then compile the generated code and then double–check if the code prepared for the development server is the same as the code for the production server.

You need not deploy the generated code manually in a source or target server. ODI prepares a package for the development environment.

You must deploy the generated code manually in a source or target server. You must copy all procedures generated into the development, test, and production servers.

Their definition is imported with a reverse–engineering process directly from databases and other sources, but you must manually define all keys and constraints existing on the database.

Their definition is imported with a reverse–engineering process directly from databases and other sources.

For every load the definition of the tables used, their columns and constraints must be manually built.

An external engine must be run to describe what metadata is needed for a Mapping.

Create new submodels and drag data stores individually to each submodel.

Use automatic distribution feature at the models level to automatically create the submodels and move the data stores based on their names.

Create new submodels and leverage the automatic distribution feature at the submodels level to automatically move the data stores based on their names.

Create new models, drag the data stores individually to each model and then drag the models to the parent model to create submodels.

Add a parallel step, add three serial steps underneath it, then add A to the first parallel step, B to the second one, and C to the last one.

Create a scenario from the variable and add the scenario to the load plan to create a case step.

Add a parallel step, add two parallel steps underneath it, then add A and B to one parallel step, and C to the other.

Add a parallel step, add two serial steps underneath it, then add A and B to one serial step, and C to the other.

ODI automatically computes the load order based on the order on which the data stores were added to the Mapping.

You can use the Target Order field.

You can use the Target Load Order field.

You can use the Load Order field.

Duplicate the Integration Knowledge Module, add an option CUSTOM_TEMPLATE, and set it within the Mapping.

Duplicate the Check Knowledge Module, add an option CUSTOM_TEMPLATE, and set it within the Mapping.

In the Physical tab of a Mapping, click one of the source data stores, select the Extract Options, and enter the SQL statement in the CUSTOM_TEMPLATE field.

Duplicate the Loading Knowledge module, add an option CUSTOM_TEMPLATE, and set it within the Mapping.

The intermediate integration table prefixed with I$ is required to determine which records must be inserted.

If Flow Control is not necessary, an I$ table is not created.

The intermediate integration table prefixed with I$ is created because the flow control is mandatory when doing an initial load.

Neither the LKM nor the IKM create intermediate tables. Most of their work is performed in the ODI Agent memory.

The execution should be done only on the development data environment, as long as the other environment is a mirrored copy.

Only the production environment can be used.

All environments linked to a logical schema can be used to reverse–engineer table structures.

Only a Java engine intermediate environment can be processed.

Yes, by adding a constraint to the datastore

No,it is not possible to add conditions more than those that can be reverse–engineered.

Yes, but you need to execute additional scripts on the database in order to make it work.

No, you can declare them only customizing knowledge modules.

Link the last step of the package to its first step to create an infinite loop.

Create a scenario from the package, add the scenario as the last step in the package, run it asynchronously, and then save and regenerate this scenario.

Create a scenario from the package, add the scenario as the last step in the package, run it asynchronously, and then save.

Drag the package to the last step in the package, run it asynchronously, and then save.

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.

Add a case step and drag the variable into the case step.

Create a scenario from the variable and add the scenario to the load plan to create a case step.

Add a case step in the load plan and select a variable in the wizard.

Drag the variable into the load plan and define a case step.

Add an OdiSendMailstep to My Package and link the My Third Package step to it by using a green OK arrow.

Add an OdiSendMailstep to My Package and link the My Last Package step to it by using a green OK arrow.

Add an OdiReadMailstep to My Package and link the My Third Package step to it by using a red KO arrow.

Add an OdiSendMailstep to My Package and link the My Third Package step to it by using a red KO arrow.

by using Upgrade Assistant

by using ODI Studio

by using Domain Creation Assistant

by using Configuration Wizard

Select the Secure Value check box.

Select the Hide Value check box.

Set the Keep History field to No History.

Leave the Default Value field empty.

Evaluate Variable

Set Variable

Declare Variable

Refresh Variable

by using a custom Groovy script

by using a variable

by using the Timeout filed

by using a Timeout knowledge module

Use Consistent CDC, do not perform a purge of the journal data when the first Mapping gets executed, and manually change the JRN_SUBSCRIBER column in the corresponding J$ table to keep the changed data present for the second Mapping.

Create a third mapping to copy the changed data to a staging table, which is used as the source of the second Mapping.

Duplicate the source data store for each Mapping.

Create two distinct subscribers for each Mapping.

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, operating systems, or scripting engines for execution.

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

It is not possible to use a specific partition.

Only ODI variables can be used to filter the target table loading.

An option in the Mapping can be used to declare partitions but an ODI variable must be used to evaluate the correct partition value.

An option in the Mapping can be used to declare the partition that has to be used for the loading.

odiRef.getSession()

odiRef.getInfo()

odiRef.getPrevStepLog()

odiRef.getStep()

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.