QUESTION: 21

Which statement about the .NETCompute Node is true?

The exception is propagated through a predefined output terminal.
.NETCompute node does not support dynamic terminal. All terminals are predefined.
The message assembly contains four trees to represent the message, the environment, the local environment and the exception list.
Only when the message needs to be transformed through the .NETCompute node, an Evaluate method is needed. In the case of the message pass-through, there is no need for an Evaluate method.

Answer(s): A

Explanation:

The Failure Terminal is the output terminal to which the input message is routed if an unhandled exception occurs during the computation.

Reveal Solution Next Question

On a Linux system, trace node is configured with Destination set to a file. The trace node should be executed if a message processes successfully. A message is processed through the Integration flow successfully but no file is written. How can the problem be determined?

This error only happens if the file system is full.
Check the console logs (stderr/stdout) for any errors.
The only way to debug this problem is to start the flow debugger.
Check the local system error logs to see if there were any errors encountered while writing to the trace node output file.

Answer(s): D

Explanation:

Note: Set the destination of the trace record that is written by the node to User Trace, Local Error Log, or File.

Reference:

https://www.ibm.com/support/knowledgecenter/en/SSMKHH_10.0.0/com.ibm.etools.mft.doc/ag66270_.htm

Reveal Solution Next Question

QUESTION: 23

Which statement is true regarding globally coordinated XA transactions with the broker?

JMS transactions do not support X
The coordinatedTransaction flag must be set in the BAR file for enabling XA transactions with the broker.
lt does not require the configuration of the queue manager to coordinate XA transactions with the broker.
When message flows participate in transactions with MQ as well as a Database, unless XA transactions are enabled, the flow can commit the database transaction but not the MQ transaction.

Answer(s): B

Reveal Solution Next Question

QUESTION: 24

A service interacts with a backend system which replies with a message correlation. When processing request/response messages from the backend, no messages were received by the flow.

Which may be the probable cause of failure?

The transaction was set to automatic on the MQOutput Node.
The developer should have used the MQInput Node instead of the MQGet Node.
The Integration Node is configured in a MQ cluster for load balancing and the object descriptor is set to the ReplyToQueueManager.
The backend request/reply message processing can only be accomplished by breaking up the flow into two flows.

Answer(s): A

Explanation:

When you define an MQOutput node, the option that you select for the Transaction Mode property defines whether the message is written under sync point:
If you select Yes, the message is written under sync point (that is, within a WebSphere MQ unit of work).

If you select Automatic (the default), the message is written under sync point if the incoming input message is marked as persistent.
If you select No, the message is not written under sync point.

Reveal Solution Next Question

Free C9530-001 Exam Braindumps (page: 6)

QUESTION: 21

Explanation:

QUESTION: 22

Explanation:

Reference:

QUESTION: 23

QUESTION: 24

Explanation: