28 Must Know Mulesoft Interview Questions

Mulesoft is a cloud integration platform for integrating Cloud and on-premise heterogeneous applications.

Anypoint Exchange is the IDE interface to search API assets and resources which can be added to our processes. We can test APIs and generate sample payloads.

Mule Runtime Is an environment (App Server) to deploy and manage mule applications with runtime manager.

Mule ESB is an architecture framework that can be used to integrate multiple applications using the bus-like infrastructure. Each can use different protocols.

RAML is a short form of Restful API Modelling Language. RAML is used to describe REST services. It uses JSON.

AnyPoint platform is a hybrid integration cloud platform on which we can create an application network of data and services .

It is a desktop IDE to develop our integration which can be deployed on cloudhub.

In short, SOAP is heavy and REST is light with payload. Refer to this article for a more detailed explanation.

A connector is used in integration process application to define what protocol to be used and if any parameters. once deployed the service endpoint can be called as per the protocol specified.

We can save the credential in the local properties file and configure it for encryption while deploying.

There are five types of Exception Handling in MuleSoft.
Choice Exception Handling.
Default Exception Handling.
Global Exception Handling.
Rollback Exception Handling.
Catch Exception Handling.

Fan-out: The Fan-Out primitive is used to fire the output terminal once or multiple times. Fan-Out can be used independently or with Fan-In.

Fan-in: Fan-in helps in taking a decision to continue flow execution. Until a decision point is reached the last message is sent to the output terminal. It can also be used with Fan-Out.

these are
HTTP, AJAX, SMTP, IMAP and JMS

scatter-gather or batch jobs can be used to do parallel processing in mulesoft.

We can use flatten dataweave function to merge two arrays into one.

SDO – Service data objects which represent variables and objects. 
SMO- Service Model Object and it uses SDO for messages.

UMO is Universal Message Object; UMO components are also referred to as service components. 

When the mediation primitive requires passing the value from the request flow to response flow the correlation context plays the role. 

Available resources are
Independent Configuration
A Mule instance is capable of loading multiple independent configuration files one after another.
Inherited Configuration
As the term inheritance referred to represent the parent and child relationships between the instances this configuration also showcases the parent-child relationship between two configurations.
It strongly provides this dependency with the guarantee that no configuration file will be omitted at the time of application booting. It used the same name for the parent and child models. 

Service Invoke:
Service invoke is an initial process of creating a service for either request or response flow.
Multiple instances of a service can be created and permitted into a flow, that allows a series of services to operate within the flow.  
CallOut:
CallOut method is to receive messages and request the required service and operation in a flow. There is a CallOut node always presented into the median flow for connected target operation.

Message Routing Service.
Message Transformation Service.
Set of Service Container.
Web Service Security.

It is used to stop the particular path inflow without generating any exception.
Fail: Generates a failure in the flow.

There are three different types of mule variables.
Record variable.
Session variable.
Flow variable.

The characteristics are:

-The global service name is applied for referring to the endpoint.
-It helps in clarifying the usage of particular destinations.
-The global endpoint is not typified or outbound routing.
-It is used in configuration files at different locations.

The supported languages of MuleSoft are:
Python.
Groovy.
Ruby.
Javascript.

Choice Router is a dynamic router which routes the messages inflow. The message content is evaluated based on a set of DataWeave expressions.

Filters help routers in making smart decisions on message delivery or request and response environment. It also provides insights to the router for deciding what to do with the messages in the transit stage.

By using Fan-in and Fan-out primitive.