Pass the MuleSoft Certified Architect MCIA-Level-1 Questions and answers with ExamsMirror

Parallel Execution:

In a Scatter-Gather scope, all routes are executed in parallel. This allows multiple operations to be performed simultaneously, which can improve performance and efficiency when dealing with independent tasks.

Transaction Management:

When Scatter-Gather operates within a local transaction, all database operations performed in parallel routes are part of the same transaction context.

Error Handling and Rollback:

If any error occurs within any of the parallel routes inside the Scatter-Gather scope, it triggers a rollback of all the database operations performed within the transaction. This ensures data consistency and integrity.

References:

MuleSoft Documentation on Scatter-Gather

Transaction management in MuleSoft

=========================

Explanation

V2 Rest API is recommended for on premise applications to access Object Store. It also comes with overhead of encryption and security of using rest api. With Object Store v2, the API call is localized to the same data center as the Runtime Manager app.

But in this case requirement is to access the OS of other mule application and not the same mule application.

You can configure a Mule app to use the Object Store REST API to store and retrieve values from an object store in another Mule app.

However, Object Store v2 is not designed for app-to-app communication.

Explanation

Before we answer this question , we need to understand what median (50th percentile) and 80th percentile means. If the 50th percentile (median) of a response time is 500ms that means that 50% of my transactions are either as fast or faster than 500ms.

If the 90th percentile of the same transaction is at 1000ms it means that 90% are as fast or faster and only 10% are slower. Now as per upstream SLA , 99th percentile is 800 ms which means 99% of the incoming requests should have response time less than or equal to 800 ms. But as per one of the backend API , their 95th percentile is 1000 ms which means that backend API will take 1000 ms or less than that for 95% of. requests. As there are three API invocation from upstream API , we can not conclude a timeout that can be set to meet the desired SLA as backend SLA's do not support it.

Let see why other answers are not correct.

1) Do not set a timeout --> This can potentially violate SLA's of upstream API

2) Set a timeout of 100 ms; ---> This will not work as backend API has 100 ms as median meaning only 50% requests will be answered in this time and we will get timeout for 50% of the requests. Important thing to note here is, All APIs need to be executed sequentially, so if you get timeout in first API, there is no use of going to second and third API. As a service provider you wouldn't want to keep 50% of your consumers dissatisfied. So not the best option to go with.

*To quote an example: Let's assume you have built an API to update customer contact details.

- First API is fetching customer number based on login credentials

- Second API is fetching Info in 1 table and returning unique key

- Third API, using unique key provided in second API as primary key, updating remaining details

* Now consider, if API times out in first API and can't fetch customer number, in this case, it's useless to call API 2 and 3 and that is why question mentions specifically that all APIs need to be executed sequentially.

3) Set a timeout of 50 ms --> Again not possible due to the same reason as above Hence correct answer is No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

Anypoint MQ is a cloud-based messaging service provided by MuleSoft. It is designed to work within MuleSoft's cloud ecosystem, which can impose certain limitations that might prevent its use in some scenarios:

Message Broker Must Be Hosted On-Premises:

Anypoint MQ is a cloud service and cannot be hosted on-premises. If a company requires its message broker to be hosted within its own data center for security, compliance, or other reasons, Anypoint MQ would not be suitable.

Ability for a Third Party Outside the Company's Network to Consume Events from the Queue:

Anypoint MQ is designed to work primarily within the Anypoint Platform ecosystem. While it does support external consumers, it requires proper security configurations, and there may be limitations or additional steps needed to securely expose queues to third-party systems outside the company's network.

References

MuleSoft Documentation: Anypoint MQ

MuleSoft Anypoint MQ Overview

To address the reliability and scalability issues faced by the insurance provider, adding a load balancer and configuring additional servers in a cluster configuration is the optimal solution. Here's why:

Load Balancing: Implementing a load balancer will help distribute incoming API requests evenly across multiple servers. This prevents any single server from becoming a bottleneck, thereby improving the overall performance and reliability of the system.

Cluster Configuration: By setting up a cluster configuration, you ensure that multiple servers work together as a single unit. This provides several benefits:

High Availability: If one server goes down, the load balancer can redirect traffic to other available servers in the cluster, minimizing downtime.

Scalability: Additional servers can be added to the cluster to handle increased load as the business grows.

Fault Tolerance: Clustering allows for automatic failover and recovery, ensuring that applications remain available even if one server fails.

Maintenance: With a cluster configuration, servers can be taken offline for maintenance one at a time without affecting the overall availability of the applications, as the load balancer can redirect traffic to the remaining servers.

VM Queues and Object Stores: In a clustered environment, the use of VM queues and object stores can be more efficiently managed as these resources are distributed across multiple servers, reducing the risk of contention and improving throughput.

References:

MuleSoft Documentation on Clustering: https://docs.mulesoft.com/mule-runtime/4.3/clustering

Best Practices for Scaling Mule Applications: https://blogs.mulesoft.com/dev/mule-dev/mule-4-scaling-applications/

A MuleSoft developer can use Anypoint Studio to implement an API as a Mule application, run the application locally, and execute unit tests against the running application. Anypoint Studio is an integrated development environment (IDE) for designing, building, testing, and deploying Mule applications. It provides tools for local development and testing, including MUnit for creating and running unit tests, making it a comprehensive solution for developing MuleSoft applications.

References:

Anypoint Studio Overview

Using MUnit for Unit Testing

Explanation

* Semantic Versioning is a 3-component number in the format of X.Y.Z, where :

X stands for a major version.

Y stands for a minor version:

Z stands for a patch.

So, SemVer is of the form Major.Minor.Patch Coming to our question , minor version of the API has been changed which is backward compatible. Hence there is no change required on API client end. If they want to make use of new featured that have been added as a part of minor version change they may need to change code at their end. Hence correct answer is The API client code ONLY needs to be changed if it needs to take advantage of new features.

Diagram Description automatically generated

According to MuleSoft’s recommended REST conventions, the HTTP method GET should be used to specify how API clients can request data from a specified resource. The GET method is designed to retrieve data from a server at the specified resource. It is one of the most common HTTP methods used in RESTful APIs, ensuring that data retrieval is performed without any side effects on the server or resource.

References:

MuleSoft REST API Design Best Practices

HTTP Methods in RESTful Services

Both Service Oriented Architecture (SOA) and API-led connectivity emphasize the principle of service reusability. This principle involves designing services and APIs in a way that they can be reused across different applications and use cases, reducing redundancy and improving efficiency. By creating reusable services, organizations can accelerate development, maintain consistency, and reduce costs associated with developing and maintaining multiple similar services.

References:

MuleSoft's API-led Connectivity Approach

Service-Oriented Architecture (SOA) Principles

Explanation

Correct answer is Database polling continues Only HTTP requests sent to the remaining node continue to be accepted. Explanation : Architecture descripted in the question could be described as follows.When node 1 is down , DB polling will still continue via node 2 . Also requests which are coming directly to node 2 will also be accepted and processed in BAU fashion. Only thing that wont work is when requests are sent to Node 1 HTTP connector. The flaw with this architecture is HTTP clients are sending HTTP requests directly to individual cluster nodes. By default, clustering Mule runtime engines ensures high system availability. If a Mule runtime engine node becomes unavailable due to failure or planned downtime, another node in the cluster can assume the workload and continue to process existing events and messages

Diagram Description automatically generated