A leading bank implementing new mule API.
The purpose of API to fetch the customer account balances from the backend application and display them on the online platform the online banking platform. The online banking platform will send an array of accounts to Mule API get the account balances.
As a part of the processing the Mule API needs to insert the data into the database for auditing purposes and this process should not have any performance related implications on the account balance retrieval flow How should this requirement be implemented to achieve better throughput?

• A.Implement the Async scope fetch the data from the backend application and to insert records in the Audit database
• B.Implement a for each scope to fetch the data from the back-end application and to insert records into the Audit database
• C.Implement a try-catch scope to fetch the data from the back-end application and use the Async scope to insert records into the Audit database
• D.Implement parallel for each scope to fetch the data from the backend application and use Async scope to insert the records into the Audit database

Comment: *

Name: *

Email: *

Verification: *

As part of a growth strategy, a supplier signs a trading agreement with a large customer. The customer sends purchase orders to the supplier according to the ANSI X12 EDI standard, and the supplier creates the orders in its ERP system using the information in the EDI document.
The agreement also requires that the supplier provide a new RESTful API to process request from the customer for current product inventory level from the supplier' s ERP system.
Which two fundamental integration use cases does the supplier need to deliver to provide an end-to-end solution for this business scenario? (Choose two.)

• A.Synchronized data transfer
• B.Sharing data with external partners
• C.User interface integration
• D.Streaming data ingestion
• E.Data mashups

Comment: *

Name: *

Email: *

Verification: *

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 pictures driving the organization to automate this process using efficient CI/'CD pipeline.
Considering Anypoint platforms capabilities how should the organization approach automating is API lifecycle?

• A.Use runtime manager rest apis for API management and mavenforAPI deployment
• B.Use Maven with a custom configuration required for the API lifecycle
• C.Use Anypoint CLI or Anypoint Platform REST apis with scripting language such as groovy
• D.Use Exchange rest api's for API management and MavenforAPI deployment

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.
A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all API implementations are Mule applications executing in a customer -hosted Mule runtime.
End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.
What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?
A)
The web store backend, being a Java EE application, automatically makes use of the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using HTTP-standard headers No special code or configuration is included in the web store backend, Experience API, and Process API implementations to generate and manage the correlation ID B) The web store backend generates a new correlation ID value at the start of checkout and sets it on the X- CORRELATlON-lt HTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID C) The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store backend in the HTTP response, which includes it in all subsequent API invocations to the Experience API.
The Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header D) The web store backend sends a correlation ID value in the HTTP request body In the way required by the Experience API The Experience API and Process API implementations must be coded to receive the custom correlation ID In the HTTP requests and propagate It in suitable HTTP request headers

• A.Option A
• B.Option B
• C.Option C
• D.Option D

Comment: *

Name: *

Email: *

Verification: *

An organization has chosen Mulesoft for their integration and API platform.
According to the Mulesoft catalyst framework, what would an integration architect do to create achievement goals as part of their business outcomes?

• A.agree upon KPI's and help develop and overall success plan
• B.evangelize API's
• C.build and publish foundational assets
• D.Measure the impact of the centre for enablement

Comment: *

Name: *

Email: *

Verification: *