MuleSoft Certified Architect MCIA-Level-1 Release Date

Explanation

* Organization should continue to use SCM system of their choice, in addition to keeping source code for these asset types in Anypoint Exchange, thereby enabling parallel development, branching.

* Reason is that Anypoint exchange is not full fledged version repositories like GitHub.

* But at same time it is tightly coupled with Mule assets

To securely consume compressed and digitally signed files from a partner's FTPS server, the following inputs are required:

• PGP Public Key of the Partner:
• PGP Private Key for the Company:
• FTP Username and Password:

By using these inputs, the Mule application can securely connect to the FTPS server, verify the integrity and authenticity of the files using PGP, and decrypt the contents for further processing.

References

• MuleSoft FTPS Connector
• MuleSoft PGP Module

Explanation

● Option A says "Perform EACH DB insert in a SEPARATE DB transaction". In this case if first DB insert is successful and second one fails then first insert won't be rolled back causing inconsistency. This option is ruled out.

● Option D says Perform BOTH DB inserts in ONE DB transaction.

Rule of thumb is when one or more DB connections are required we must use XA transaction as local transactions support only one resource. So this option is also ruled out.

● Option B acknowledges the before DB processing, so message is removed from the queue. In case of system failure at later point, message can't be retrieved.

● Option C is Valid: Though it says "do not ack JMS message", message will be auto acknowledged at the end of transaction. Here is how we can ensure all components are part of XA transaction:

Additional Information about transactions:

● XA Transactions - You can use an XA transaction to group together a series of operations from multiple transactional resources, such as JMS, VM or JDBC resources, into a single, very reliable, global transaction.

● The XA (eXtended Architecture) standard is an X/Open group standard which specifies the interface between a global transaction manager and local transactional resource managers.

The XA protocol defines a 2-phase commit protocol which can be used to more reliably coordinate and sequence a series of "all or nothing" operations across multiple servers, even servers of different types

● Use JMS ack if

– Acknowledgment should occur eventually, perhaps asynchronously

– The performance of the message receipt is paramount

– The message processing is idempotent

– For the choreography portion of the SAGA pattern

● Use JMS transactions

– For all other times in the integration you want to perform an atomic unit of work

– When the unit of work comprises more than the receipt of a single message

– To simply and unify the programming model (begin/commit/rollback)

To reduce the overall development time to release the System API, the most efficient approach is to use the Anypoint Connector for Salesforce. This connector is specifically designed to interact with Salesforce APIs, providing a seamless and optimized way to access customer data directly from Salesforce. Using this connector simplifies development, reduces complexity, and leverages built-in capabilities for authentication and data retrieval, ensuring a faster and more secure implementation.

References:

• Anypoint Connector for Salesforce
• Connecting to Salesforce with Anypoint Platform