Free WSO2 Enterprise-Integrator-6-Developer Practice Exam with Questions & Answers | Set: 2

RESTAPI

Pipeline

Sequence

Proxy service

Write a Script mediator.

Write a custom mediator.

Write an Axis2 handler.

Write a custom message builder and formatter.

None of these approaches would implement this scenario.

Use the Switch mediator.

Write a custom Class mediator and implement the custom routing logic inside that mediator.

Use the Script mediator and implement the above routing logic.

Create a separate endpoints CAR file for each environment (Dev, QA, Prod) and deploy the endpoints CAR and the ESB profile configurations CAR file.

All of the above approaches can be used for externalizing endpoints.

Parameterize the endpoints values and replace those with matching endpoint values at build time using a Maven project.

Externalize and store the endpoints in the registry and refer to them by name in the ESB profile configuration.

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.

This happens when a soapll message is sent to a soapl2 endpoint or vice versa, resulting in the p, message content type not matching the SOAP namespace URI, e.g., soapll should have text/xml content type and soapl2 should

have application/soap+xml content type. Solution: Enable the relevant message builder/formatter in axis2.xml for the matching content type.

The ESB profile has failed to extract the transport protocol from the given URL. This happens when theO transport defined in the URL is not enabled in the system. Solution: Enable relevant transport sender in axis2.xml.

This happens when a soapll message is sent to a soapl2 endpoint or vice versa. Solution: Correct the SOAP envelope namespace.

Options a, b and c all provide mismatching reasons/solutions, so all of the answers are incorrect.

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.

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.

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

ESB profilesupports 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).

Write a Class mediator.

Write a Synapse handler.

Write a custom messagebuilder and formatter.

Use the Script mediator.