Enterprise-Integrator-6-Developer WSO2 Certified Enterprise Integrator 6 Developer (6.5 version) Questions and Answers

The Exception mediator can be used to customize error messages that are send back to the client.

It is mandatory to associate each sequence and proxy service with a fault sequence.

Within the fault sequence, you can access error details using the EXCEPTION_DETAIL property.

A fault sequence is a collection of mediators just like any other sequence, and it can be associated with another sequence or a proxy service.

The method\"isContentAware\" in the mediator specifies whether the mediator requires the message to be built in order to perform the mediator action.

If the mediator is content-unaware, it will always build the message.

It is the mediator's ability to identify the messaging format and select matching message builders and formatters.

All of the above.

Using message store/message processor constructs, guaranteed message delivery can be implemented.

Using message store/message processor constructs, the dead letter channel pattern can be implemented.

Using message store/message processor constructs, in-order delivery of messages cannot be implemented.

Using message store/message processor constructs, message throttling can be implemented.

It will discard already existing requests and start the shutdown steps immediately.

The graceful shutdown command is only available from the management console.

Each profile uses the same key store and trust store.

It will stop accepting new requests, process all existing requests, and then shut down.

< task name=\"CheckPrice\n class=\"org.wso2.esb.tutorial.tasks.PlaceStockOrderTask\" >

< trigger interval=\"1800\7 >

< /task >

< task name=\"CheckPrice\" class=\"org.wso2.esb.tutorial.tasks.PlaceStockOrderTask\"

< trigger interval=\"30\", continuous=\"true\7 >

< /task >

< task name=\"CheckPrice\n class=\"org.wso2.esb.tutorial.tasks.PlaceStockOrderTask\" >

trigger interval=\"30\7 >

< /task >

All three configurations are incorrect.

Any JMS consumer application cannot consume messages from a given store. Only message processors can consume messages in a JMS message store.

Both a and b are correct.

The ESB profile supports the store-and-forward pattern but not guaranteed delivery.

Users have the option to create a custom message store with their own message store implementation.

When retry count is 0.

When the suspend timeout is reached.

When there is a response from the endpoint.

When the retry count is a positive integer.

Endpoints are used to define external destinations of a message.

The same endpoint cannot be used with multiple transports.

An endpoint can be defined independently of transports.

Once configurations are defined, the endpoint can be used to connect to any external service.

Messaging systems introduce additional programming complexity.

Messaging systems do not guarantee when the message will be delivered, which can cause sequencing issues.

Performance issues due to the overhead added to the communication by message systems.

Operation is disconnected from networks. Data is synchronized when network connection is available.

Message Filter

Dynamic Router

Content Filter

Composed Msg. Processor

Integration is much faster than using sequences and proxy services.

Connectors cannot be directly added and removed to the runtime, so after deploying them you have to restart the servers.

No extensive knowledge of the source system is required to use ESB connectors.

150+ connectors are available, and WS02 is continuously adding more to the connector collection.

The ESB profile can be configured as both a JMS Producer and Consumer.

JMS supports point-to-point communication models only.

The ESB profile can be configured as a shared topic listener.

Both statements a and c are correct.

ESB profile supports the store and forward messaging model with JMS.

ESB profile supports the point-to-point messaging model (queue).

All of the above are supported by the ESB profile.

ESB profile supports the publish/subscribe messaging model (topics).

Mutual SSL provides message level security.

Mutual SSL provides higher performance.

All of the above are correct.

Both client and server have to authenticate each other and require certificates to be configured at both server and client ends.

JavaScript

Ruby

XSLT

Groovy

Proxy services should be implemented as pure Java classes.

Only HTTP and HTTPS transports can be used to receive and send messages from the proxy services.

Proxy services allow you to perform necessary transformations and introduce additional functionality without changing your existing service.

A proxy service is not externally visible and can't be accessed using a URL similar to a normal web service address.

For debugging purposes, you want to introduce some latency in the message flow.

You want to change just a single element in the XML payload without changing other elements.

For testing purposes, you want to record the elapsed time between calling a backend service and receiving the response by the proxy service.

You want to develop a logging mediator that sends logging data to an external database such as MySQL.

JMS distributed transactions are supported in the ESB profile.

The transport.jms.SessionTransacted property is used to enable JMS local transactions in the ESB profile.

ESB profile JMS transactions only work with either the Callout mediator or the Call mediator in blocking mode.

Only JMS local transactions are supported in the ESB profile.

API

Inbound endpoint

Proxy service

Message processor

. Message Channels

Pipes and Filters

Composed Msg. Processor

Message Translator

If it is a class mediator, you can put that JAR file in the < EI_HOME > /lib directory.

If you have developed your custom mediator as a regular non-OSGI JAR, you have to put it in the < EI_HOME > /extensions directory.

All of the above.

If you have developed your custom mediator as an OSGI bundle, you have to put it in the < EI_HOME > /dropins directory.