An organization is designing Mule application which connects to a legacy backend. It has been reported that backend services are not highly available and experience downtime quite often. As an integration architect which of the below approach you would propose to achieve high reliability goals?

• A. Until Successful scope can be implemented while calling backend API's
• B. Alerts can be configured in Mule runtime so that backend team can be communicated when services are down
• C. Create a batch job with all requests being sent to backend using that job as per the availability of backend API's
• D. On Error Continue scope to be used to call in case of error again

An organization has just developed a Mule application that implements a REST API. The mule application will be deployed to a cluster of customer hosted Mule runtimes.
What additional infrastructure component must the customer provide in order to distribute inbound API requests across the Mule runtimes of the cluster?

• A. A message broker
• B. An Object Store
• C. A database
• D. An HTTP Load Balancer

Which Mulesoft feature helps users to delegate their access without sharing sensitive credentials or giving full control of accounts to 3rd parties?

• A. Connected apps
• B. Secure Scheme
• C. client id enforcement policy
• D. Certificates

A travel company wants to publish a well-defined booking service API to be shared with its business partners.
These business partners have agreed to ONLY consume SOAP services and they want to get the service contracts in an easily consumable way before they start any development. The travel company will publish the initial design documents to Anypoint Exchange, then share those documents with the business partners. When using an API-led approach, what is the first design document the travel company should deliver to its business partners?

• A. Create a SOAP API specification in Design Center
• B. Create a RAML API specification using any text editor
• C. Create a WSDL specification using any XML editor
• D. Create an OAS API specification in Design Center

An organization has an HTTPS-enabled Mule application named Orders API that receives requests from another Mule application named Process Orders.
The communication between these two Mule applications must be secured by TLS mutual authentication (two-way TLS).
At a minimum, what must be stored in each truststore and keystore of these two Mule applications to properly support two-way TLS between the two Mule applications while properly protecting each Mule application's keys?

• A. Orders API truststore: The Orders API private key and public key
  Process Orders keystore: The Process Orders private key public key
• B. Orders API truststore: The Process Orders public key
  Orders API keystore: The Orders API private key and public key
  Process Orders truststore: The Orders API public key
  Process Orders keystore: The Process Orders private key and public key
• C. Orders API truststore: The Orders API public key
  Process Orders keystore: The Process Orders private key and public key
• D. Orders API truststore: The Process Orders public key
  Orders API keystore: The Orders API private key
  Process Orders truststore: The Orders API public key
  Process Orders keystore: The Process Orders private key