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

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.

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.

. Message Channels

Pipes and Filters

Composed Msg. Processor

Message Translator

JavaScript for processing messages at a given message sequence.

Synapse configuration language.

WS02 EItooling.

Java code to build the entire message processing logic.

When looking up secured passwords in a Synapse configuration, it is possible to use theXPath expression ,,wso2:vault-lookup('alias,) to retrieve the actual password by providing 'alias'.

Secure vault can be used to secure plain text passwords stored in ESB profile configuration files.

Secure vault uses the cipher-tool.properties filesto identify the locations of the passwords in configuration U files.

Secure vault always uses the certificate in the primary keystore configured in carbon.xml to encrypt the passwords.

FTPS, FTP, HTTPS

HTTP, HTTPS

All of the above

MQTT

The SHA 256 hash of the JDBC connection URL of the registry database.

The value you entered for the element.

The SHA 255 hash of the value you gave to the element.

The JDBC connection URL of the registry database.

Data Mapper mediator can perform JSON-to-JSON transformation without converting the message to a canonical form.

All the transformation mediators require SOAP as the canonical message format.

Enrich mediator cannot be used for message transformation.

Header mediator can only work with SOAP headers.