Free WSO2 Enterprise-Integrator-6-Developer Practice Exam with Questions & Answers

JavaScript for processing messages at a given message sequence.

Synapse configuration language.

WS02 EItooling.

Java code to build the entire message processing logic.

Both statement b and c are correct.

It is not possible to set parameters for custom mediators.

Custom mediator's parameters should be declared as public fields in mediator code. For instance: public String foo, bar;

Synapse properties can be used to pass values to mediator arguments. For instance:

</class name=\"org.wso2.custom.HelloClassMediator\">

<property name=\Mfoo\M value=\"10\"/>

<property name=\Mbar\n value=\"5\"/>

</class>

Custom Synapse Handler by extending AbstractSynapseHandler

Custom transport by implementing org.apache.axis2.transport.base.AbstractTransportSender and org.apache.axis2.transport.base.AbstractTransportListener interfaces

All of the above

Custom class mediator byextending AbstractMediator.

If you do not define a fault sequence, in the case of an error in a sequence or a proxy service, an exception will be thrown and the message will be dropped.

In situationswhere a fault sequence is not specified explicitly, a default fault sequence will be used to handle errors.

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

The Fault mediator can be used to customize error messages that are sent back to the client.

The client should obtain the OAuth access token from the authorization server and send it as an HTTP header in the resource request to the ESB profile.

Client has to register with the authorization server.

OAuthmediator can work with any authorization server to verify the OAuth access token.

OAuth mediator does the OAuth access token verification against an authorization server.

All of the above are correct.

Throttling isonly supported at the mediation level.

The throttle mechanism is used to control access to the services at different levels.

Mediation level throttling works in distributed fashion only when ESB nodes are configured as a stateful cluster which is a membership based cluster.

O

All three configurations are incorrect.

O

O

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.

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 responseby the proxy service.

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

SSL outbound profiles allow different SSL profiles for different backend servers.

Each ssl profile uses the same keystore and truststore.

Inbound SSL profiles allow you to specify different SSL profiles for different IPs of clients

The purpose of SSL profiles is to allow connections to different servers with different certificates and identities.