A REST API is being designed to implement a Mule application.What standard interface definition language can be used to define REST APIs?
Answer(s): B
In a Mule Application, a flow contains two (2) JMS consume operations that are used to connect to a JMS broker and consume messages from two(2) JMS destination. The Mule application then joins the two JMS messages together.The JMS broker does not implement high availability (HA) and periodically experiences scheduled outages of upto 10 mins for routine maintenance.What is the most idiomatic (used for its intented purpose) way to build the mule flow so it can best recover from the expected outages?
Answer(s): A
When an operation in a Mule application fails to connect to an external server, the default behavior is for the operation to fail immediately and return a connectivity error. You can modify this default behavior by configuring a reconnection strategy for the operation. You can configure a reconnection strategy for an operation either by modifying the operation properties or by modifying the configuration of the global element for the operation. The following are the available reconnection strategies and their behaviors: None Is the default behavior, which immediately returns a connectivity error if the attempt to connect is unsuccessful Standard (reconnect) Sets the number of reconnection attempts and the interval at which to execute them before returning a connectivity error Forever (reconnect-forever) Attempts to reconnect continually at a given interval
A Mule application name Pub uses a persistence object store. The Pub Mule application is deployed to Cloudhub and it configured to use Object Store v2.Another Mule application name sub is being developed to retrieve values from the Pub Mule application persistence object Store and will also be deployed to cloudhub.What is the most direct way for the Sub Mule application to retrieve values from the Pub Mule application persistence object store with the least latency?
Answer(s): D
* The Object Store V2 API enables API access to Anypoint Platform Object Store v2.* 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. To share data between two Mule4 apps, use a queue in Anypoint MQ.* The Object Store v2 APIs enable you to use REST to perform the following:- Retrieve a list of object stores and keys associated with an application.- Store and retrieve key-value pairs in an object store.- Delete key-value pairs from an object store.- Retrieve Object Store usage statistics for your organization.- Object Store provides these APIs:Object Store APIObject Store Stats API
https://docs.mulesoft.com/object-store/osv2-apisAdditional Info:When to use Object Store and when to use VM
An organization uses a four(4) node customer hosted Mule runtime cluster to host one(1) stateless api implementation. The API is accessed over HTTPS through a load balancer that uses round-robin for load distribution. Each node in the cluster has been sized to be able to accept four(4) times the current number of requests.Two(2) nodes in the cluster experience a power outage and are no longer available. The load balancer directs the outage and blocks the two unavailable the nodes from receiving further HTTP requests.What performance-related consequence is guaranteed to happen to average, assuming the remaining cluster nodes are fully operational?
* "100% increase in the throughput of the API" might look correct, as the number of requests processed per second might increase, but is it guaranteed to increase by 100%? Using 4 nodes will definitely increase throughput of system. But it is cant be precisely said if there would be 100% increase in throughput as it depends on many other factors. Also it is nowhere mentioned in the description that all nodes have same CPU/memory assigned. The question is about the guaranteed behavior * Increasing number of nodes will have no impact on response time as we are scaling application horizontally and not vertically. Similarly there is no change in JVM heap memory usage. * So Correct answer is 50% reduction in the number of requests being received by each node This is because of the two reasons. 1) API is mentioned as stateless 2) Load Balancer is used
In Anypoint Platform, a company wants to configure multiple identity providers(Idps) for various lines of business (LOBs) Multiple business groups and environments have been defined for the these LOBs. What Anypoint Platform feature can use multiple Idps access the company's business groups and environment?
Correct answer is Client Management* Anypoint Platform acts as a client provider by default, but you can also configure external client providers to authorize client applications.* As an API owner, you can apply an OAuth 2.0 policy to authorize client applications that try to access your API. You need an OAuth 2.0 provider to use an OAuth 2.0 policy.* You can configure more than one client provider and associate the client providers with different environments. If you configure multiple client providers after you have already created environments, you can associate the new client providers with the environment.* You should review the existing client configuration before reassigning client providers to avoid any downtime with existing assets or APIs.* When you delete a client provider from your master organization, the client provider is no longer available in environments that used it.* Also, assets or APIs that used the client provider can no longer authorize users who want to access them.-------------------------------------------------------------------------------------------------------------MuleSoft
https://docs.mulesoft.com/access-management/managing-api-clients https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html
Post your Comments and Discuss Salesforce MuleSoft-Integration-Architect-I exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the MuleSoft-Integration-Architect-I content, but please register or login to continue.