1Z0-448 ODI (No cloud)

Question

Identify two implementation strategies of changed data capture provided through ODI Knowledge Modules. (Choose two.)

Answer 1

Extracting source data to flat files

Answer 2

Oracle GoldenGate

Answer 3

Before–and–after database image comparison

Answer 4

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

Answer 5

Directly from the source database to the target database

Answer 6

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

Answer 7

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

Answer 8

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.

Answer 9

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.

Answer 10

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.

Answer 11

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

Answer 12

Use a dedicated schema such as ODI_STAGING

Answer 13

Use the same schema as the Data Schema

Answer 14

Use SYSTEM

Answer 15

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

Answer 16

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.

Answer 17

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

Answer 18

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

Answer 19

By using Opatch

Answer 20

By using the import/export utilities

Answer 21

By using ODI Studio

Answer 22

By using Upgrade Assistant

Answer 23

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

Answer 24

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

Answer 25

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

Answer 26

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

Answer 27

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

Answer 28

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

Answer 29

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

Answer 30

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

Answer 31

The project must be explicitly mapped within an ODI mapping.

Answer 32

A customize knowledge module is needed.

Answer 33

An ODI procedure must be associated with it.

Answer 34

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

Answer 35

All distinct entries are processed.

Answer 36

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

Answer 37

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

Answer 38

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

Answer 39

alphanumeric

Answer 40

Data transformation must be distributed across several scalable nodes.

Answer 41

It is mandatory to have an intermediate server.

Answer 42

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

Answer 43

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

Answer 44

OdiWaitForData

Answer 45

OdiWaitForCDCData

Answer 46

OdiWaitForLogData

Answer 47

OdiWaitForTable

Answer 48

Oracle BPEL Process Manager

Answer 49

Oracle GoldenGate

Answer 50

ODI Console

Answer 51

Oracle WebLogic Server

Answer 52

transform only

Answer 53

load and transform

Answer 54

extract and load

Answer 55

extract and transform

Answer 56

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.

Answer 57

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.

Answer 58

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.

Answer 59

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.

Answer 60

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

Answer 61

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

Answer 62

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

Answer 63

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

Answer 64

This works only for Oracle and Informix.

Answer 65

This works only for Oracle and MySQL.

Answer 66

Create a new generic technology to support it.

Answer 67

Use the out–of the box Generic SQL technology.

Answer 68

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

Answer 69

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.

Answer 70

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

Answer 71

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

Answer 72

This option is inherited from reverse engineering.

Answer 73

This option is always available.

Answer 74

You can never make this choice.

Answer 75

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

Answer 76

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

Answer 77

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.

Answer 78

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.

Answer 79

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.

Answer 80

high availability

Answer 81

minimal footprint

Answer 82

access to WebLogic connection pools

Answer 83

management in Enterprise Manager Cloud Control

Answer 84

OdiOutFile

Answer 85

OdiFileCopy

Answer 86

OdiFileMove

Answer 87

ODI Runtime Agent

Answer 88

ODI Standalone Agent

Answer 89

ODI JEE Agent

Answer 90

ODI Colocated Standalone Agent

Answer 91

conditions

Answer 92

foreign keys

Answer 93

primary keys

Answer 94

alternate keys

Answer 95

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

Answer 96

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

Answer 97

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

Answer 98

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

Answer 99

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

Answer 100

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

Answer 101

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

Answer 102

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

Answer 103

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.

Answer 104

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.

Answer 105

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.

Answer 106

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.

Answer 107

Restart from new session.

Answer 108

Restart from failure.

Answer 109

Restart from failed children.

Answer 110

Restart all children.

Answer 111

Consistent set journalizing runs faster than simple journalizing.

Answer 112

Consistent set journalizing always uses Oracle Golden Gate.

Answer 113

Consistent set journalizing treats each data store individually.

Answer 114

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

Answer 115

odiMasterRepository

Answer 116

MasterRepository

Answer 117

odimasterrepository

Answer 118

ODIMasterRepository

Answer 119

Create a procedure and add two tasks.

Answer 120

Create a Knowledge Module.

Answer 121

Create a counter variable.

Answer 122

Create a procedure

Answer 123

Regenerate the existing scenario

Answer 124

Nothing, the existing scenario will automatically be updated.

Answer 125

Generate a new scenario and create a new schedule.

Answer 126

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

Answer 127

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

Answer 128

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

Answer 129

It is used to load data between Teradata and Oracle.

Answer 130

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

Answer 131

Run Exception and Restart

Answer 132

Run Exception and Continue

Answer 133

Run Exception and Ignore

Answer 134

Run Exception and Fail

Answer 135

Run Exception and Raise

Answer 136

They contain project and security information.

Answer 137

They contain data models and execution information.

Answer 138

They contain data and security information.

Answer 139

They contain data models and project information.

Answer 140

Use OdiPingAgent in a package to ping AGT agent.

Answer 141

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

Answer 142

In Topology, test the connections to the AGT agent.

Answer 143

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

Answer 144

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.

Answer 145

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.

Answer 146

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.

Answer 147

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.

Answer 148

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

Answer 149

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

Answer 150

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

Answer 151

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

Answer 152

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

Answer 153

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

Answer 154

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

Answer 155

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

Answer 156

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

Answer 157

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

Answer 158

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

Answer 159

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.

Answer 160

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

Answer 161

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

Answer 162

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

Answer 163

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

Answer 164

Datastores

Answer 165

Knowledge Modules

Answer 166

Reusable Mappings

Answer 167

the schema hosting the Work repository

Answer 168

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

Answer 169

the schema hosting the Staging Area

Answer 170

They contain data model and security information.

Answer 171

They contain security and topology information.

Answer 172

They contain project and topology information.

Answer 173

They contain project and security information.

Answer 174

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

Answer 175

The Knowledge Module must be customized only for aggregation functions.

Answer 176

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

Answer 177

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

Answer 178

Only an Integration Knowledge Module single–technology is required.

Answer 179

Only an Integration Knowledge Module multitechnology is required.

Answer 180

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

Answer 181

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

Answer 182

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

Answer 183

It is not possible to enforce constraints on any technology.

Answer 184

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

Answer 185

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.

Answer 186

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

Answer 187

./agent.sh –NAME=OracleDIAgent1

Answer 188

./startComponent.sh OracleDIAgent1

Answer 189

./startComponent.sh OracleDIAgent1 –PORT=20910

Answer 190

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.

Answer 191

Add an OdiSendMail step to a knowledge module.

Answer 192

Duplicate the OdiSendMail step into multiple packages.

Answer 193

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

Answer 194

They can have generic input and output signatures.

Answer 195

They contain both a Logical and Physical Mapping design.

Answer 196

They can be used within regular Mappings.

Answer 197

They can be executed directly.

Answer 198

They can be shared across projects.

Answer 199

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

Answer 200

All transformations are executed on the staging area.

Answer 201

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

Answer 202

All expressions are executed on the source area.

Answer 203

on the Coherence Server

Answer 204

on the Administration Server

Answer 205

on the Node Manager

Answer 206

on the Managed Server

Answer 207

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.

Answer 208

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.

Answer 209

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

Answer 210

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.

Answer 211

Oracle GoldenGate primarily performs aggregations for ODI.

Answer 212

Oracle GoldenGate and ODI are used together primarily for running weekly batch jobs.

Answer 213

Oracle GoldenGate provides non–invasive changed data capture capabilities to ODI.

Answer 214

ODI starts and stops Oracle GoldenGate processes automatically during a Mapping execution.

Answer 215

ODI and Oracle GoldenGate enable real–time business intelligence.

Answer 216

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.

Answer 217

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

Answer 218

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

Answer 219

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

Answer 220

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

Answer 221

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

Answer 222

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

Answer 223

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

Answer 224

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.

Answer 225

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

Answer 226

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

Answer 227

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

Answer 228

ODI Console allows administrators to edit users’ information.

Answer 229

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

Answer 230

ODI sessions can be monitored in Enterprise Manager Cloud Control.

Answer 231

ODI Console provides access to project and mapping details.

Answer 232

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

Answer 233

You can use the Target Order field.

Answer 234

You can use the Target Load Order field.

Answer 235

You can use the Load Order field.

Answer 236

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

Answer 237

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

Answer 238

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.

Answer 239

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

Answer 240

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

Answer 241

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

Answer 242

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

Answer 243

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

Answer 244

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

Answer 245

Only the production environment can be used.

Answer 246

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

Answer 247

Only a Java engine intermediate environment can be processed.

Answer 248

Yes, by adding a constraint to the datastore

Answer 249

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

Answer 250

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

Answer 251

No, you can declare them only customizing knowledge modules.

Answer 252

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

Answer 253

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.

Answer 254

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

Answer 255

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

Answer 256

restart from failed tasks

Answer 257

exception handling

Answer 258

native support for parallelism

Answer 259

support for Open Tools

Answer 260

restart of an agent

Answer 261

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

Answer 262

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.

Answer 263

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.

Answer 264

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.

Answer 265

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

Answer 266

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

Answer 267

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

Answer 268

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

Answer 269

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

Answer 270

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

Answer 271

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

Answer 272

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

Answer 273

by using Upgrade Assistant

Answer 274

by using ODI Studio

Answer 275

by using Domain Creation Assistant

Answer 276

by using Configuration Wizard

Answer 277

Select the Secure Value check box.

Answer 278

Select the Hide Value check box.

Answer 279

Set the Keep History field to No History.

Answer 280

Leave the Default Value field empty.

Answer 281

Evaluate Variable

Answer 282

Set Variable

Answer 283

Declare Variable

Answer 284

Refresh Variable

Answer 285

by using a custom Groovy script

Answer 286

by using a variable

Answer 287

by using the Timeout filed

Answer 288

by using a Timeout knowledge module

Answer 289

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.

Answer 290

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

Answer 291

Duplicate the source data store for each Mapping.

Answer 292

Create two distinct subscribers for each Mapping.

Answer 293

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

Answer 294

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

Answer 295

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

Answer 296

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

Answer 297

It is not possible to use a specific partition.

Answer 298

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

Answer 299

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

Answer 300

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

Answer 301

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

Answer 302

ODI performs data transformations inside a Hadoop cluster.

Answer 303

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

Answer 304

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

Answer 305

odiRef.getSession()

Answer 306

odiRef.getInfo()

Answer 307

odiRef.getPrevStepLog()

Answer 308

odiRef.getStep()

Answer 309

Create one Logical Schema per Physical Schema.

Answer 310

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

Answer 311

Create one Logical Schema per Data Server.

Answer 312

Create one Logical Schema per Context.

	Criado por Dani Rodrigáñez quase 5 anos atrás

Próximo

1Z0-448 ODI (No cloud)

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Questão 29

Questão 30

Questão 31

Questão 32

Questão 33

Questão 34

Questão 35

Questão 36

Questão 37

Questão 38

Questão 39

Questão 40

Questão 41

Questão 42

Questão 43

Questão 44

Questão 45

Questão 46

Questão 47

Questão 48

Questão 49

Questão 50

Questão 51

Questão 52

Questão 53

Questão 54

Questão 55

Questão 56

Questão 57

Questão 58

Questão 59

Questão 60

Questão 61

Questão 62

Questão 63

Questão 64

Questão 65

Questão 66

Questão 67

Questão 68

Questão 69

Questão 70

Questão 71

Questão 72

Questão 73

Questão 74

Questão 75

Questão 76