1z0-448 Sample Questions Answers

on the Coherence Server

on the Administration Server

on the Node Manager

on the Managed Server

OdiOutFile

OdiFileCopy

OdiFileMove

OdiInFile

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.

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.

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.

Go to the Physical tab, select theFixedDesign check boxof 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 theModify check boxof the Physical Mapping Design.

Use Consistent CDC, do not perform a purge of the journal data when the first Mapping gets executed, and manually change theJRN_SUBSCRIBERcolumn in the correspondingJ$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.

Their definition is imported with areverse-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.

Forevery 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.

high availability

minimal footprint

access to WebLogic connection pools

management in Enterprise Manager Cloud Control

Regenerate the existing scenario.

Nothing, the existing scenario will automaticallybe updated.

Generate a new scenario and create a new schedule.

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

Run Exception and Restart

Run Exception and Continue

Run Exception and Ignore

Run Exception and Fail

Run Exception and Raise

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.

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.

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.

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.

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

./agent.sh –NAME=OracleDIAgent1

./startComponent.sh OracleDIAgent1

./startComponent.sh OracleDIAgent1 –PORT=20910

numeric

alphanumeric

date

text

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.

by using Upgrade Assistant

by using ODI Studio

by using Domain Creation Assistant

by using Configuration Wizard

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.