QUESTION: 105

Mule application is deployed to Customer Hosted Runtime. Asynchronous logging was implemented to improved throughput of the system. But it was observed over the period of time that few of the important exception log messages which were used to rollback transactions are not working as expected causing huge loss to the Organization. Organization wants to avoid these losses. Application also has constraints due to which they cant compromise on throughput much.
What is the possible option in this case?

Logging needs to be changed from asynchronous to synchronous
External log appender needs to be used in this case
Persistent memory storage should be used in such scenarios
Mixed configuration of asynchronous or synchronous loggers should be used to log exceptions via synchronous way

Answer(s): D

Explanation:

Correct approach is to use Mixed configuration of asynchronous or synchronous loggers shoud be used to log exceptions via synchronous way Asynchronous logging poses a performance-reliability trade-off. You may lose some messages if Mule crashes before the logging buffers flush to the disk. In this case, consider that you can have a mixed configuration of asynchronous or synchronous loggers in your app. Best practice is to use asynchronous logging over synchronous with a minimum logging level of WARN for a production application. In some cases, enable INFO logging level when you need to confirm events such as successful policy installation or to perform troubleshooting. Configure your logging strategy by editing your application's src/main/resources/log4j2.xml file

Reveal Solution Next Question

QUESTION: 106

As a part of business requirement , old CRM system needs to be integrated using Mule application. CRM system is capable of exchanging data only via SOAP/HTTP protocol. As an integration architect who follows API led approach , what is the the below step you will perform so that you can share document with CRM team?

Create RAML specification using Design Center
Create SOAP API specification using Design Center
Create WSDL specification using text editor
Create WSDL specification using Design Center

Answer(s): C

Explanation:

Correct answer is Create WSDL specification using text editor SOAP services are specified using WSDL. A client program connecting to a web service can read the WSDL to determine what functions are available on the server. We can not create WSDL specification in Design Center. We need to use external text editor to create WSDL.

Reveal Solution Next Question

QUESTION: 107

Insurance organization is planning to deploy Mule application in MuleSoft Hosted runtime plane. As a part of requirement , application should be scalable . highly available. It also has regulatory requirement which demands logs to be retained for at least 2 years. As an Integration Architect what step you will recommend in order to achieve this?

It is not possible to store logs for 2 years in CloudHub deployment. External log management system is required.
When deploying an application to CloudHub , logs retention period should be selected as 2 years
When deploying an application to CloudHub, worker size should be sufficient to store 2 years data
Logging strategy should be configured accordingly in log4j file deployed with the application.

Answer(s): A

Explanation:

Correct answer is It is not possible to store logs for 2 years in CloudHub deployment. External log management system is required. CloudHub has a specific log retention policy, as described in the documentation: the platform stores logs of up to 100 MB per app & per worker or for up to 30 days, whichever limit is hit first. Once this limit has been reached, the oldest log information is deleted in chunks and is irretrievably lost. The recommended approach is to persist your logs to a external logging system of your choice (such as Splunk, for instance) using a log appender. Please note that this solution results in the logs no longer being stored on our platform, so any support cases you lodge will require for you to provide the appropriate logs for review and case resolution

Reveal Solution Next Question

QUESTION: 108

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?

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

Answer(s): B

Explanation:

Correct answer is Untill Successful scope can be implemented while calling backend API's The Until Successful scope repeatedly triggers the scope's components (including flow references) until they all succeed or until a maximum number of retries is exceeded The scope provides option to control the max number of retries and the interval between retries The scope can execute any sequence of processors that may fail for whatever reason and may succeed upon retry

Reveal Solution Next Question

Free MuleSoft-Integration-Architect-I Exam Braindumps (page: 27)

QUESTION: 105

Explanation:

QUESTION: 106

Explanation:

QUESTION: 107

Explanation:

QUESTION: 108

Explanation: