The implementation of a Process API must change. What is a valid approach that minimizes the impact of this change on API clients?
* Option B shouldn't be used unless extremely needed, if RAML is changed, client needs to accommodate changes. Question is about minimizing impact on Client. So this is not a valid choice.
* Option C isn't valid as Business can't stop for consumers acknowledgment.
* Option D again needs Client to accommodate changes and isn't viable option.
* Best choice is A where RAML definition isn't changed and underlined functionality is changed without any dependency on client and without impacting client.
A stock broking company makes use of CloudHub VPC to deploy Mule applications. Mule application needs to connect to a database application in the customers on-premises corporate data center and also to a Kafka cluster running in AWS VPC.
How is access enabled for the API to connect to the database application and Kafka cluster securely?
In one of the critical payment related mule application, transaction is being used . As an enhancement to implementation , scatter gather route is introduced which is also the part of transaction group. Scatter gather route has 4 routes.
What will be the behavior of the Mule application in case of error occurs in 4th route of the scatter-gather router and transaction needs to be rolled back?
* Scatter Gather: When running within a transaction, Scatter Gather does not execute in parallel. This means that the second route is executed after the first one is processed, the third after the second one, etc. In case of error, all routes will be rolled back
An organization is designing a mule application to support an all or nothing transaction between serval database operations and some other connectors so that they all roll back if there is a problem with any of the connectors
Besides the database connector , what other connector can be used in the transaction.
Correct answer is VM VM support Transactional Type. When an exception occur, The transaction rolls back to its original state for reprocessing. This feature is not supported by other connectors.
Here is additional information about Transaction management:

What is a defining characteristic of an integration-Platform-as-a-Service (iPaaS)?
Amy Baker
3 days agoElizabeth Harris
7 days agoKimberly Taylor
1 month agoCharles Cooper
1 month agoBarbara Peterson
2 months agoGeorge Cook
2 months agoJeffrey Taylor
3 months agoMargaret Scott
3 months agoNancy Jackson
4 months agoRonald Jackson
5 months agoMargaret Rivera
4 months agoSharon Bell
4 months agoChristopher Reed
4 months agoCarol Williams
4 months agoDennis Hill
4 months agoDana
5 months agoFrance
5 months agoLelia
6 months agoJudy
6 months agoShawnee
6 months agoMan
7 months agoMaryanne
7 months agoMarion
7 months agoSina
7 months agoTaryn
8 months agoShayne
8 months agoBarrie
8 months agoRicarda
8 months agoHarley
9 months agoGregoria
9 months agoMan
9 months agoBulah
9 months agoDarnell
10 months agoFiliberto
10 months agoErnie
10 months agoErinn
10 months agoBette
11 months agoAja
11 months agoJettie
11 months agoGrover
11 months agoDulce
12 months agoShad
12 months agoGoldie
1 year agoStevie
1 year agoMariann
1 year agoElsa
1 year agoLeonardo
1 year agoDulce
1 year agoElfrieda
1 year agoPamella
1 year agoMartha
1 year agoChara
1 year agoMerrilee
1 year agoCelestina
1 year agoLynda
1 year agoAlona
1 year agoChauncey
2 years agoTwana
2 years agoThurman
2 years agoBrynn
2 years agoMozell
2 years agoJeanice
2 years agoMaricela
2 years agoBarrie
2 years agoDenna
2 years agoShalon
2 years agoPamella
2 years agoMelissia
2 years agoErnie
2 years agoDierdre
2 years agoJoni
2 years agoCaprice
2 years agoShenika
2 years agoAndra
2 years agoScarlet
2 years agoMozelle
2 years agoHannah
2 years agoLauran
2 years agoCory
2 years agoKenny
2 years agoWilda
2 years agoHelaine
2 years agoLaurel
2 years agoEdelmira
2 years agoAlonzo
2 years agoOmega
2 years agoNakisha
2 years agoTonja
2 years agoLelia
2 years agoLucina
2 years agoDulce
2 years agoBettyann
2 years agoChu
2 years ago