Certified MuleSoft Integration Architect IPreview

Refer to the exhibits.
An Order microservice and a Fulfillment microservice are being designed to communicate with their clients through message-based integration (and NOT through API invocations).
The Order microservice publishes an Order message (a kind of command message) containing the details of an order to be filled. The intent is that Order messages are only consumed by one Mule application: the Fulfillment microservice.
The Fulfillment microservice consumes Order messages, fills the orders described therein, and then publishes a Fulfillment message (a kind of event message). Each Fulfillment message can be consumed by any interested Mule application, and the Order microservice is one such Mule application.
What is the recommended choice of message broker(s) and message destination(s) in this scenario?

An organization is struggling with frequent version upgrades and external plugin project dependencies. The team wants to minimize the impact on applications by creating best practices that will define a set of default dependencies across all new and in-progress projects.
How can these best practices be achieved with the applications having the least amount of responsibility?

Following MuleSoft’s recommended best practices for API governance and API policies, a project team has used RAML specifications to document and publish functional requirements and detailed design definitions of its APIs. These API specifications have been used by various stakeholders to implement APIs.
Later, the project team requires all API specifications to be augmented with an additional non-functional requirement (NFR) to protect the backend services from a high rate of requests, according to defined service-level agreements (SLAs). The NFR’s SLAs are based on a new tiered subscription level “Gold”, “Silver”, or “Platinum” that must be tied to a new parameter that is being added to the Accounts object in their enterprise data model.
Following MuleSoft’s recommended best practices, how should the project team now convey the necessary non-functional requirement to stakeholders?

A Mule application is required to periodically process a large data set from a back-end database to Salesforce CRM using a Batch Job scope configured properly to process the high rate of records. The Mule applications is deployed to two CloudHub 1.0 workers with the persistent VM queues option disabled (unchecked).
What is the consequence if a worder that is processing records from a Batch Job scope crashes during records processing?

A Mule solution implements an Experience API and System API as Mule applications that process messages in this order:

1. Experience API receives a request Anypoint MQ message (REQU) with a payload containing a variable-length list of request objects.
2. The Experience API uses a For Each scope to split the list into individual objects and sends each object a REQU_OBJECT message to an
   Anypoint MQ queue named REQUEST.
3. The Sytem API listens on the REQUEST queue, processes each message independently of all other messages, and sends a response message to a response queue named RESPONSE_OBJECT.
   The System API processing times can vary and are occasionally fairly long.
4. The Experience API listens on the RESPONSE_OBJECT queue and receives, transforms, and accumulates each response.
5. After receiving all the responses corresponding to the original REQU message, the Experience API creates and publishes a response Anypoint MQ message (RESP) to an Anypoint MQ queue named RESPONSE with a payload containing the list of responses returned by the System API, organized in the same order as the request objects originally sent in the REQU message.
   Assume successful response messages are returned by Experience API to the RESPONSE queue for all REQU messages.
   What is required so the Experience API can ensure the length and order of the list of objects in RESP and REQU match, while at the same time maximizing message throughput?

An organization is the process of building automated deployments using a CI/CD process. As a part of automated deployments, it wants to apply policies to API instances.
What tool can the organization use to promote and deploy API Manager policies?

A project team is working on an API implementation using an API RAML specification as a starting point. The team has updated the RAML specification to include new operations, and has published a new version to Exchange. Meanwhile, another team is working on an API client Mule application to consume the same API implementation.
During this development, what must be performed by the Mule application team to take advantage of the newly added operations?

An architect is designing a Mule application to meet the following two requirements:

1. The application must process files asynchronously and reliably from an FTPS server to a back-end database using VM intermediary queues for load-balancing Mule events.
2. The application must process a medium rate of records from a source to a target system using a Batch Job scope.
   To make the Mule application more reliable, the Mule application will be deployed to two CloudHub 1.0 workers.
   Following MuleSoft-recommended best practices, how should the Mule application deployment typically be configured in Runtime Manger to best support the performance and reliability goals of both the Batch Job scope and the file processing VM queues?

An organization is successfully using API-led connectivity. However, as the application network grows, all the manually performed tasks to publish, share and discover, register, apply policies to, and deploy an API are becoming repetitive, which is driving the organization to automate this process using efficient CI/CD pipelines.
Considering Anypoint Platform’s capabilities, how should the organization automate its API lifecycle?

An organization has strict unit test requirements that mandate every Mule application must have an MUnit test suite with a test case defined for each flow and a minimum test coverage of 80 percent.
A developer is building an MUnit test suite for a newly developed Mule application that sends API requests to an external REST API.
What is an effective approach for successfully executing the MUnit tests of this Mule application while still achieving the required test coverage for the MUnit tests?

A cluster with two customer-hosted Mule runtimes is hosting an application that has a flow with a JMS listener configured to subscribe to messages from a topic destination.
How should the JMS listener’s primaryNodeOnly parameter and subscription parameter be configured so the JMS listener can receive messages in all the nodes of the cluster but only process each message once?

A retail company is implementing a MuleSoft API to get inventory details from two vendors by invoking each vendor’s online applications. Due to network issues, the invocations to the vendor applications are timing out intermittently, but the requests are successful after re-invoking each vendor application.
What is the most performant way of implementing the API to invoke each vendor application and to retry invocations that generate timeout errors?

A stock trading company handles millions of trades a day and requires excellent performance and reliability within its stock trading system. The company operates a number of event-driven APIs implemented as Mule applications that are hosted on various customer-hosted Mule clusters and needs to enable message exchanges between the APIs within their internal network using shared message queues.
What is an effective way to meet the cross-cluster messaging requirements of its event-driven APIs?

A Mule application uses an HTTP Request operation to invoke an external API. The external API follows the HTTP specification for proper status code usage.
What is a possible cause when a 3xx status code is returned to the HTTP Request operation from the external API?

A Mule application is synchronizing customer data between two different database systems.
What is a main benefit of using eXtended Architecture (XA) transactions rather than local transactions to synchronize these two different database systems?

An external API frequently invokes an Employees system API to fetch employee data from a MySQL database. The architect must design a caching strategy to query the database only when there is an update to the Employees table or else return a cached response in order to minimize the number of redundant transactions being handled by the database.
What must the architect do to achieve the caching objective?

A corporation has deployed Mule applications to different customer-hosted Mule runtimes. Mule applications deployed to these Mule runtimes are managed by Anypoint Platform.
What needs to be installed or configured (if anything) to monitor these Mule applications from Anypoint Monitoring, and how is monitoring data from each Mule application sent to Anypoint Monitoring?

When a Mule application using VM queues is deployed to a customer-hosted cluster or multiple CloudHub v1.0 workers/replicas, how are messages consumed across the nodes?

An organization has built a large monolithic application over the years and is currently looking to transition to a microservices architecture. During this transition phase, it has built some System APIs as Mule applications that provide access to different pieces of functionality of the monolithic application. The System APIs are deployed to Mule runtimes in a customer-hosted EC2 instance in AWS.
The System API communicate directly with one database used by the monolithic application. Currently, a Database connector and configuration for that connector must be built into every project. There is a plan to partition this database into various smaller data stores in the future.
What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?

An organization is designing multiple Mule applications to run on CloudHub in a single Anypoint VPC and that must share data using a common persistent Anypoint Object Store v2 (OSv2).
What design gives these Mule applications access to the same Object Store instance?

A bank is implementing a REST API in a Mule application to receive an array of accounts from an online banking platform user interface (UI), retrieve account balances for those accounts from a backend Finance system, and then return the account balances so they can be displayed in the online banking platform UI. As part of the processing, the MuleSoft API also needs to insert the retrieved account data into an Audit Database for auditing purposes. The auditing process should not add latency to the account balance retrieval response back to the online banking platform UI.
The retrieveBalances flow in the Mule application is designed to use an operation in a connector to the Finance system (the Finance operation) that can only look up one account record at a time, and an operation from a different connector to the Audit system (the Audit operation) that can only insert one account record at a time.
To best meet the performance-related requirements, what scope or scopes should be used and how should they be used to incorporate the Finance operation and Audit operation into the retrieveBalances flow?

A payment processing company has implemented a Payment Processing API Mule application to process credit card and debit card transactions. Because the Payment Processing API handles highly sensitive information, the payment processing company requires that data must be encrypted both in-transit and at-rest.
To meet these security requirements, consumers of the Payment Processing API must create request message payloads in a JSON format specified by the API, and he message payload values must be encrypted.
How can the Payment Processing API validate requests received from API consumers?

A company is modernizing its legacy systems to accelerate access to applications and data while supporting the adoption of new technologies. The key to achieving this business goal is unlocking the company’s systems and data, including a set of existing services hosted on-premises that can be accessed by authorized external clients. The IT staff is mainly experienced only with supporting its legacy systems.
Considering the current aggressive backlog and the project delivery requirements, the company wants to take a strategic approach in the first phase of its transformation projects by quickly deploying APIs in Mule runtimes that are able to scale, connect to on-premises systems, and migrate as needed.
Following MuleSoft best practices, what MuleSoft runtime deployment option best meets the company’s goals to begin its digital transformation journey?