IBM WebSphere Enterprise Service Bus V7.0, Integration Development - C9550-605 Exam Practice Test

A. The message is lost and no recovery can be performed.

B. The message can be manually recovered from the failed event manager and sent to the target service.

C. The message can be manually recovered from the System Exception Destination and sent to the target service.

D. The message is automatically recovered and sent to the target service.

A. Copy the function java cods into the value field of type java expression.

B. Add the utility jar as a dependency using the dependency editor of the module containing the component to be tested.

C. Add the utility.jar as a dependency using the dependency editor of the component test project

D. Add the utility.jar to a library included in the dependency editor of the module containing the component to be tested.

A. Use serviceDeploy command inside exec task.

B. Use serviceDeployLight task.

C. Use appCreate task.

D. Use serviceDeploy task.

A. In the code of the Java Snippet, ensure the relevant imports are declared.

B. Select the module and File->Import->JAR file and import the utils.jar file.

C. In the Java Imports tab of the Custom Mediation primitive, ensure the relevant imports are declared.

D. In the Java Build path of the module, ensure that the relvant JARs are included.

A. A Flow Order primitive has one input terminal and can have any number of output terminals.

B. Each output terminal of a Flow Order primitive is executed with an input message modified by the previous branch.

C. The output terminals are executed in the order that they are defined on the primitive, with each branch completing before the next starts.

D. The properties of a Flow Order primitive can be promoted to be configured at runtime.

E. A Flow Order primitive must be used at the beginning of a mediation request/response flow.

A. a project interchange file.

B. a command-line service deployment zip file.

C. a JAR file.

D. an EAR file.

A. A Stop primitive would stop the execution and consume the message silently; a Fail primitive would stop the execution, throw an exception and may rollback global transactions if configured.

B. A Stop primitive would stop the execution, throw an exception and consume the message; a Fail primitive would stop the execution and may return the message to the downstream primitive through its output terminal if configured.

C. A Stop primitive would stop the execution and may return the message to the downstream primitive through its output terminal if configured; a Fail primitive would stop the execution, throw an exception and may return the message to the downstream primitive through its output terminal if configured.

D. A Stop primitive would stop the execution, throw an exception and may rollback global transactions if configured; a Fail primitive would stop the execution and consume the message silently.

A. Project Interchange (PI) file. Then import the PI file into WebSphere Integration Developer V7.0, and step through the migration wizard.

B. shared EAR file. Import the EAR file into WebSphere Integration Developer V7.0, which will automatically migrate the project.

C. Project Interchange file. Then use the serviceDeploy Tool in WebSphere Integration Developer V7.0 to migrate the project.

D. JAR file. Import the JAR file into WebSphere Integration Developer V7.0, which will automatically migrate the project.

A. Both ServicePurchaseOrder and ServicePurchaseOrderLine objects should be created ServicePurchaseOrder should not inherit from PurchaseOrder ServicePurchaseOrderLine should inherit from PurchaseOrderLine

B. Both ServicePurchaseOrder and ServicePurchaseOrderLine objects should be created ServicePurchaseOrder should inherit from PurchaseOrder ServicePurchaseOrderLine should inherit from PurchaseOrderLine

C. Only a ServicePurchaseOrderLine object should be created ServicePurchaseOrderLine should inherit from PurchaseOrderLine

D. Only a ServicePurchaseOrder object should be created ServicePurchaseOrder should inherit from PurchaseOrder

A. Set

B. Assign

C. Append

D. Move

A. Select the 'WS-I attachment profile 1.0 swaRef schema file' interface in the Predefined Resources section of the dependency editor of the module.

B. Create a custom interface that follows the WS-I Attachment Profile 1.0 in a library and add it in the library section of the dependency editor of the module.

C. Add a custom interface with a field 'attachment' to an export and when generating the WS binding select the '(WS-I) Attachment Profile 1.0 with swaRef' option.

D. Add the predefined SwaRefLib in the library section of the dependency editor of the module.

A. The 'Asynchronous invocation' qualifier of the StatusServiceIFPartner' reference is set to 'Commit' while it must be set to 'Call'.

B. The 'Transaction' qualifier of the 'ModuleA' implementation is set to 'Global' while it must be set to 'Local'.

C. The 'Join transaction' qualifier of the 'TargetServiceIFPartner' interface is set to 'True' while it must be set to 'False'.

D. The 'Join transaction' qualifier of the 'StatusServiceIF' interface is set to 'False' while it must be set to 'True'.

A. Correlation context defined in the Message Element Setter primitive of the request flow.

B. Shared context defined in the Message Element Setter primitive of the request flow.

C. Shared context defined in the Input node of the request flow.

D. Correlation context defined in the Input node of the request flow.