MuleSoft-Integration-Architect-I 무료 덤프문제 온라인 액세스

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?

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

A company is planning to extend its Mule APIs to the Europe region. Currently all new applications are deployed to Cloudhub in the US region following this naming convention
{API name}-{environment}. for example, Orders-SAPI-dev, Orders-SAPI-prod etc.
Considering there is no network restriction to block communications between API's, what strategy should be implemented in order to apply the same new API's running in the EU region of CloudHub as well to minimize latency between API's and target users and systems in Europe?

• A.Set region property to Europe (eu-de) in API manager for all the mule applicationChange the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users
• B.Set region property to Europe (eu-de) in runtime manager for all the mule applicationChange the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users
• C.Set region property to Europe (eu-de) in API manager for all the mule applicationNo need to change the naming convention
• D.Set region property to Europe (eu-de) in runtime manager for all the mule applicationNo need to change the naming convention

An organization is designing an integration Mule application to process orders by submitting them to a back- end system for offline processing. Each order will be received by the Mule application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a back- end system. Orders that cannot be successfully submitted due to rejections from the back-end system will need to be processed manually (outside the back-end system).
The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization's firewall. The back-end system has a track record of unreliability due to both minor network connectivity issues and longer outages.
What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the back-end system while supporting but minimizing manual order processing?

• A.An Until Successful scope to call the back-end systemOne or more ActiveMQ long-retry queuesOne or more ActiveMQ dead-letter queues for manual processing
• B.One or more On Error scopes to assist calling the back-end systemAn Until Successful scope containing VM components for long retriesA persistent dead-letter VM queue configured in CloudHub
• C.A Batch Job scope to call the back-end systemAn Until Successful scope containing Object Store components for long retriesA dead-letter object store configured in the Mule application
• D.One or more On Error scopes to assist calling the back-end systemOne or more ActiveMQ long-retry queuesA persistent dead-letter object store configured in the CloudHub Object Store service

A Mule application is built to support a local transaction for a series of operations on a single database. The mule application has a Scatter-Gather scope that participates in the local transaction.
What is the behavior of the Scatter-Gather when running within this local transaction?

• A.Execution of all routes within Scatter-Gather occurs in parallel Any error that occurs inside Scatter- Gather will be handled by error handler and will not result in roll back
• B.Execution of all routes within Scatter-Gather occurs sequentially Any error that occurs inside Scatter- Gather will result in a roll back of all the database operations
• C.Execution of all routes within Scatter-Gather occurs sequentially Any error that occurs inside Scatter- Gather will be handled by error handler and will not result in roll back
• D.Execution of all routes within Scatter-Gather occurs in parallel Any error that occurs inside Scatter- Gather will result in a roll back of all the database operations

Mule applications need to be deployed to CloudHub so they can access on-premises database systems. These systems store sensitive and hence tightly protected data, so are not accessible over the internet.
What network architecture supports this requirement?

• A.Static IP addresses for the Mule applications deployed to the CloudHub Shared Worker Cloud, plus matching firewall rules and IPwhitelisting in the on-premises network
• B.An Anypoint VPC with one Dedicated Load Balancer fronting each on-premises database system, plus matching IP whitelisting in the load balancer and firewall rules in the VPC and on-premises network
• C.Relocation of the database systems to a DMZ in the on-premises network, with Mule applications deployed to the CloudHub Shared Worker Cloud connecting only to the DMZ
• D.An Anypoint VPC connected to the on-premises network using an IPsec tunnel or AWS DirectConnect, plus matching firewall rules in the VPC and on-premises network