WSO2 Enterprise-Integrator-6-Developer WSO2 Certified Enterprise Integrator 6 Developer (6.5 version) Exam Practice Test

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.

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.

FTPS, FTP, HTTPS

HTTP, HTTPS

All of the above

MQTT

Use the XSLT mediator with the Validate mediator and send the message out with a default enpoint.

Implement message transformation with the Data Mapper and use endpoint format as soapll.

Use the XSLT mediator and use the Call mediator with blocking mode.

Use the XSLT mediator and use the Call mediator with blocking mode with enable addressing.

Use an Axis2 handler

Write a custom Class mediator

Use an API handler

Use an Axis2 module

Log mediator

Drop mediator

Validate mediator

Switch mediator

JavaScript for processing messages at a given message sequence.

Synapse configuration language.

WS02 EItooling.

Java code to build the entire message processing logic.

JavaScript

Ruby

XSLT

Groovy

The response message comes to the main sequence.

The message is sent to an endpoint from the main sequence.

Messages go through each of the mediators inside the main sequence.

If an error occurs in a sequence, the message goes through its error sequence.

Use of class variables is not recommended.

You can define and use a global variable in the mediator class if and only if those variables are shared with all the messages in that particular message flow.

When we use the mediatorin different artifacts, an instance of the mediator gets created for each occurrence in the configuration.

A mediator instance gets created for each occurrence in the configuration and for each message.

Outbound endpoints are mandatory for any integration scenario.

They operate in the same way as inbound endpoints.

When you use message stores, you have to specify the address as an outbound endpoint.

Outbound endpoints can have flags to translate the message.

Implement a custom message formatter to work with PDF payloads and register it in the /conf /axis2/axis2.xml file under the section.

Implement a custom message builder to work with PDF payloads and register it in the /conf /axis2/axis2.xml file under the section.

Both steps a and b are required.

WS02 ESB can handle PDF payloads by default, so there is no need to build a custom message builder/formatter.