Online Access Free MCIA-Level-1-Maintenance Practice Test

When the mule application using VM is deployed to a customer-hosted cluster or multiple cloudhub workers, how are messages consumed by the Mule engine?

• A.in non-deterministic way
• B.the primary only in order to avoid duplicate processing
• C.by starting an XA transaction for each new message
• D.in a deterministic way

A company 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 HTTP5 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 the rejections from the back-end system will need to be processed manually (outside the banking system).
The mule application will be deployed to a customer hosted runtime and will be 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.
Which 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.A batch job scope to call the back in system An Untill successful scope containing Object Store components for long retries. A dead-letter object store configured in the Mule application
• B.One or more on-Error scopes to assist calling the back-end system one or more ActiveMQ long-retry queues A persistent dead-letter Object store configuration in the CloudHub object store service
• C.An Until Successful scope to call the back-end system One or more ActiveMQ long-retry queues One or more ActiveMQ dead-letter queues for manual processing
• D.One or more On Error scopes to assist calling the back-end system An Untill successful scope containing VM components for long retries A persistent dead-letter VM queue configure in Cloud hub

An organization is using Mulesoft cloudhub and develops API's in the latest version. As a part of requirements for one of the API's, third party API needs to be called. The security team has made it clear that calling any external API needs to have include listing As an integration architect please suggest the best way to accomplish the design plan to support these requirements?

• A.Implement the Any point filter processor to implement the include list IP
• B.Implement the validation of includelisted IP operation
• C.Implement a proxy for the third party API and enforce the IPinclude list policy and call this proxy from the flow of the API
• D.Implement includelist IP on the cloudhub VPC firewall to allow the traffic

An organization has implemented the cluster with two customer hosted Mule runtimes is hosting an application.
This application has a flow with a JMS listener configured to consume messages from a queue destination. As an integration architect can you advise which JMS listener configuration must be used to receive messages in all the nodes of the cluster?

• A.Use the parameter primaryNodeOnly= "true" on the JMS listener
• B.Use the parameter primaryNodeOnly= "true" on the JMS listener with a non*shared subscription
• C.Use the parameter primaryNodeOnly= "false" on the JMS listener with a shared subscription
• D.Use the parameter primaryNodeOnly= "false" on the JMS listener

A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP: RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500.
What is the expected H1TP status when the client exceeds the quota of the API calls?

• A.HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end
• B.HTTP status 401 unauthorized for policy violation
• C.HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API B. HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated