1z0-448 Practice Exam Questions with Answers Oracle Data Integrator 12cEssentials Certification

the schema hosting the Work repository

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

the schema hosting the Staging Area

SYS

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.

Only an Integration KnowledgeModule single-technology is required.

Only an Integration Knowledge Module multitechnology is required.

Aloading Knowledge Module multitechnology and an IntegrationKnowledgeModule 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.

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.

They contain project and security information.

They contain data models and execution information.

They contain data and security information.

They contain data models and project information.

Variables

Datastores

Knowledge Modules

Reusable Mappings

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.

UseOdiPingAgentin 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).

Duplicate theIntegration Knowledge Module, add an optionCUSTOM_TEMPLATE, and set it within the Mapping.

Duplicate the Check Knowledge Module, add an optionCUSTOM_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 theCUSTOM_TEMPLATEfield.

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

odiMasterRepository

MasterRepository

odimasterrepository

ODIMasterRepository

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.

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.

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.

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.

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.

ODI Console allows administrators to edit users’ information.

Enterprise Manager Cloud Control provides access to ODI data servers’ settings.

ODI sessions can be monitored in Enterprise Manager Cloud Control.

ODI Console provides access to project and mapping details.

numeric

alphanumeric

date

text