Enterprise-Integrator-6-Developer Sample Questions Answers

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.

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.

trigger interval=\"30\7>

All three configurations are incorrect.

O

All three configurations are incorrect.

O

O

Periodically connect to an external service and extract some data.

Trigger some Java code when certain types of data (for instance, stock price of IBM) comes to the sequence.

Periodically run some Java code inside a sequence.

Run a piece of code just once after the ESB profile starts.

Message headers are altered but not the content.

During pass-throughmessaging, the mediation logic is completely bypassed.

The ESB profile may read the message content depending on the mediators that you have configured.

Message content is altered during mediation.

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 extensiveknowledge of the source system is required to use ESB connectors.

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

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.

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

The graceful shutdown command is onlyavailable 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.

API

Inbound endpoint

Proxy service

Message processor

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.

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.

Create a connector project and include proxy services to invoke the API provider's endpoints.

Create a connector project and write Synapse configurations that call the API provider's endpoints.

Create a connector project and use the API provider's SDK.

Both option a and b can be used.

To engage the deployed Synapse handler, you need to add a new configuration to the section to the /conf/synapse-handlers.xml file.

All of the above.

If you have developed your handler as a non-OSGI JAR file, copy it to the directory.

If you have developed your handler as an OSGI bundle, copy it to the /dropins directory.

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

JMSsupports point-to-point communication models only.

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

Both statements a and c are correct.

JavaScript for processing messages at a given message sequence.

Synapse configuration language.

WS02 EItooling.

Java code to build the entire message processing logic.

Wire-Tap

Message Translator

Content-Enricher

Splitter

Use WS02 EI with data services for database operations

DBLookup mediator

Store mediator

DBReport mediator

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.

Scripts in the Script mediator can be stored in a separate file and can be referenced from the Script mediator.

A script cannot be stored as an embedded script in the Script mediator configuration.

The script file can be stored as a local entry.

Script files can be stored in the registry.

Splitter

Facade

Wire-Tap

Dead Letter Channel