- What is Mule? …
- What are the different tools and services offered by Mulesoft? …
- What is Mule ESB? …
- What are Batch Jobs in Mule ESB? …
- What are the different types of variables in MuleSoft? …
- What are the different types of messages in MuleSoft?
MuleSoft Interview Questions and Answers (*** NEW ***) | General | Mule4
Q92. Throttling vs. Rate Limiting: What’s the Difference?
Ans. API Policies such as Rate Limiting and Throttling are available in MuleSoft, and you may use API Manager to implement them.
Rate Limiting: This policy restricts the number of requests an API can take in a certain period of time. Requests that exceed the limit will be rejected by the API.
Throttling: The Throttling policy puts requests that exceed their limitations in a queue to be processed later. If the processing fails after a specific number of attempts, the API will eventually refuse the request. You can set a retry delay and a retry limit.
mulesoft interview questions
41. What is a SOAP Web Service? Answer: SOAP simply stands for Simple Object Access Protocol. It is defined as an XML-based protocol for accessing web services. SOAP is considered as a W3C recommendation for communication between two applications. SOAP is XML based protocol. It is platform-independent and language independent. By making use of the SOAP, you will be capable interact with other programming language applications.
11. Why the Name Mule? Answer: We should know that there is a lot of infrastructural work to be done before we can really start thinking about the implementation of any logic. So this infrastructural work is regarded or termed as “donkey work” as it is needed to be done for almost every project. A Mule is also simply referred to as a carrier of loading that is moving it from one place to another. The load here specialized in moving is our information of enterprise.
Because the data is originated from multiple sources, the integration often involves the cleaning, resolving redundancy and checking against business rules for integrity. An Operational Data Store is usually designed for containing the low-level or atomic (indivisible) data (such as transactions and prices) and the data with a limited history which get as captured “real-time” or “near real-time”.
An Operational Data Store is a database which has been designed for integrating the data from multiple sources and performing the additional operations on the data, for reporting, controls and operational decision support. Unlike a production master data store, the data is not getting passed back to the operational systems. It may be passed for further operations and to the data warehouse for the reporting.
9. What is the functionality of Fan-in and Fan-out? Answer: Fan-Out: We can use the Fan out primitive for firing the output terminal once (with the input message) or firing the output terminal multiple times. You can be using the Fan out in isolation or as part of a Fan-out and Fan in combination. Fan-In: Fan In is always partnered with Fan-out in the same flow and acts as a decision point for when to continue for flow execution. It will receive a number of messages until a decision point is reached, at which the last message to be received is propagated to the output terminal. The Fan in primitive may only be used in combination with Fan-out.
Q100. What is distributed file polling, and how does it work?
Ans. Distributed file polling is used in Mule 4 to poll files across cluster nodes. This feature is enabled by default in only a few connectors.
Connectors can be configured to poll exclusively from the primary node @primaryNode Only, overriding the mule runtime engines default setting.