Reference: https://www.caeliusconsulting.com/blogs/one-way-and-two-way-tls-and-their-implementation-in- mulesoft/

Reference: https://help.mulesoft.com/s/article/Enable-external-log-forwarding-for-Mule-applications- deployed-in-RTF

When a Mule application using VM queues is deployed to a customer-hosted cluster or multiple CloudHub v1.
0 workers/replicas, messages are consumed in a non-deterministic way. This means that any of the nodes in the cluster or any of the workers can consume the messages from the VM queues, but there is no guaranteed order or specific pattern (such as round-robin or sequential processing).
This non-deterministic message consumption helps in distributing the load and handling messages more efficiently across multiple nodes or workers, improving the scalability and reliability of the application.
References
* MuleSoft Documentation on VM Queues and Clustering
* Best Practices for Deploying Mule Applications in Clusters

A). Implement HTTP caching policy for all GET endpoints for the master lookup API and implement locking to synchronize access to object store Comprehensive Detailed Step by Step Explanation To resolve the performance issue observed during the performance testing of the Master lookup API, the best approach involves caching and synchronization:
* HTTP Caching Policy:
* Purpose: Reduces the load on the database by caching the responses for GET requests. Once a response is cached, subsequent requests for the same resource can be served from the cache instead of querying the database.
* Implementation: Apply the HTTP caching policy to all GET endpoints of the Master lookup API.
This policy ensures that the frequently accessed master lookup data is stored in the cache and served quickly.
* Benefits: This significantly reduces the number of database queries, thus lowering the response time and improving performance.
* Object Store Locking:
* Purpose: Ensures data consistency and prevents race conditions when multiple workers attempt to access or update the cache concurrently.
* Implementation: Use a locking mechanism to synchronize access to the object store. This can be achieved by using MuleSoft's Object Store Connector with lock/unlock operations.
* Benefits: Prevents multiple database queries for the same key and ensures that only one worker updates the cache at a time, thus avoiding redundant operations and maintaining data integrity.
By implementing these two strategies, the response time of the Master lookup API will be significantly improved, and the performance issue will be resolved.
References
* MuleSoft HTTP Caching Policy
* MuleSoft Object Store Connector

The data format shown in the exhibit is YAML (YAML Ain't Markup Language). YAML is a human- readable data serialization standard that is commonly used for configuration files and data exchange between languages with different data structures. In the exhibit, the indentation and the use of colons to define key- value pairs are characteristic of YAML.
JSON (JavaScript Object Notation) and XML (eXtensible Markup Language) have different syntax structures, and CSV (Comma-Separated Values) is a flat file format that uses commas to separate values. The format shown in the exhibit fits the structure and style of YAML.
References
* YAML Specification Documentation
* MuleSoft Documentation on Supported Data Formats