BannerBuzz Designer Interview Questions and Answers

Transaction modes in MQ node are used to control the behavior of transactions.

• Transaction modes include 'auto', 'none', 'single', and 'multiple'

• Auto mode automatically starts a transaction for each message

• None mode disables transactions

• Single mode ensures that each message is part of a single transaction

• Multiple mode allows messages to be part of multiple transactions

• Transaction modes can be set at the node level or th

IIB uses various nodes for different purposes.

• Input nodes: HTTPInput, MQInput, FileInput, etc.

• Output nodes: HTTPOutput, MQOutput, FileOutput, etc.

• Processing nodes: Compute, Filter, Route, etc.

• Transformation nodes: Mapping, XSLT, JSON, etc.

• Utility nodes: Timer, Trace, TryCatch, etc.

• Storage nodes: Database, File, etc.

• Security nodes: SSLConfig, Authentication, etc.

There are various parsers used in webMethods Broker (WMB) such as XML, Flat File, JSON, and EDI.

• XML parser is used to parse XML messages

• Flat File parser is used to parse flat file messages

• JSON parser is used to parse JSON messages

• EDI parser is used to parse EDI messages

xmlnsc is used for defining namespaces in IBM Integration Bus, while xmlns is used in XML documents for the same purpose.

• xmlnsc is specific to IBM Integration Bus, while xmlns is a standard XML attribute.

• xmlnsc is used in message flows to define namespaces for message elements.

• xmlns is used in XML documents to define namespaces for elements and attributes.

• Both are used to avoid naming conflicts in XML documents.

No, it is not mandatory to use validate node.

• Validate node is used to validate the input data against a schema.

• It is not mandatory to use it, but it is recommended to ensure data consistency.

• Other nodes like switch, function, and change can also be used for validation.

Yes, multiple databases can be used in a flow by configuring multiple database connectors.

• Configure multiple database connectors in the flow

• Specify the database name and connection details for each connector

• Use the appropriate connector in each step of the flow based on the required database

• Data can be transferred between databases using intermediate steps

return true means a positive response while return false means a negative response.

• return true is used to indicate that a certain condition is met or an operation is successful

• return false is used to indicate that a certain condition is not met or an operation has failed

• return true and return false are often used in conditional statements and functions

• example: function isEven(num) { if(num % 2 === 0) { return true; } e

Using propagate to determines whether an exception should be propagated to the caller or not.

• If propagate to is not used, the exception will not be propagated to the caller and will be handled within the flow.

• If propagate to is used, the exception will be propagated to the caller and can be handled by the calling flow or application.

• Propagate to can be used in conjunction with exception handling nodes like Try-Catch or...read more

Messages fail and catch in MQ and SOAP nodes based on different criteria.

• In MQ nodes, messages can fail due to issues like invalid message format, queue full, or network errors.

• MQ nodes can catch messages that fail due to these issues and route them to a designated error queue.

• In SOAP nodes, messages can fail due to issues like invalid SOAP message format or authentication errors.

• SOAP nodes can catch messages that fail...read more

Yes, pub sub mechanism is a messaging pattern where senders of messages, called publishers, do not program the messages to be sent directly to specific receivers, called subscribers.

• Publishers send messages to a topic or channel without knowing which subscribers, if any, will receive the message.

• Subscribers express interest in one or more topics and only receive messages that are of interest.

• It is commonly used in dist...read more

Yes, I am cloud aware.

• I have experience working with cloud platforms such as AWS, Azure, and Google Cloud.

• I understand the benefits of cloud computing such as scalability, cost-effectiveness, and accessibility.

• I am familiar with cloud-based tools and technologies such as Docker, Kubernetes, and serverless computing.

• I have worked on projects that involve cloud-based storage, databases, and APIs.