Free MuleSoft-Integration-Architect-I Exam Braindumps
Salesforce Certified MuleSoft Integration Architect I Questions 71–75 (page: 16)

Updated On: 10-Feb-2026

A mule application is deployed to a Single Cloudhub worker and the public URL appears in Runtime Manager as the APP URL.

Requests are sent by external web clients over the public internet to the mule application App url. Each of these requests routed to the HTTPS Listener event source of the running Mule application. Later, the DevOps team edits some properties of this running Mule application in Runtime Manager. Immediately after the new property values are applied in runtime manager, how is the current Mule application deployment affected and how will future web client requests to the Mule application be handled?

  1. Cloudhub will redeploy the Mule application to the OLD Cloudhub worker New web client requests will RETURN AN ERROR until the Mule application is redeployed to the OLD Cloudhub worker
  2. CloudHub will redeploy the Mule application to a NEW Cloudhub worker
    New web client requests will RETURN AN ERROR until the NEW Cloudhub worker is available
  3. Cloudhub will redeploy the Mule application to a NEW Cloudhub worker New web client requests are ROUTED to the OLD Cloudhub worker until the NEW Cloudhub worker is available.
  4. Cloudhub will redeploy the mule application to the OLD Cloudhub worker New web client requests are ROUTED to the OLD Cloudhub worker BOTH before and after the Mule application is redeployed.

Answer(s): C

Explanation:

CloudHub supports updating your applications at runtime so end users of your HTTP APIs experience zero downtime.
While your application update is deploying, CloudHub keeps the old version of your application running. Your domain points to the old version of your application until the newly uploaded version is fully started. This allows you to keep servicing requests from your old application while the new version of your application is starting.



An external REST client periodically sends an array of records in a single POST request to a Mule application API endpoint.
The Mule application must validate each record of the request against a JSON schema before sending it to a downstream system in the same order that it was received in the array Record processing will take place inside a router or scope that calls a child flow. The child flow has its own error handling defined. Any validation or communication failures should not prevent further processing of the remaining records.
To best address these requirements what is the most idiomatic(used for it intended purpose) router or scope to used in the parent flow, and what type of error handler should be used in the child flow?

  1. First Successful router in the parent flow
    On Error Continue error handler in the child flow
  2. For Each scope in the parent flow
    On Error Continue error handler in the child flow
  3. Parallel For Each scope in the parent flow
    On Error Propagate error handler in the child flow
  4. Until Successful router in the parent flow
    On Error Propagate error handler in the child flow

Answer(s): B

Explanation:

Correct answer is For Each scope in the parent flow On Error Continue error handler in the child flow. You can extract below set of requirements from the question a) Records should be sent to downstream system in the same order that it was received in the array b) Any validation or communication failures should not prevent further processing of the remaining records First requirement can be met using For Each scope in the parent flow and second requirement can be met using On Error Continue scope in child flow so that error will be suppressed.



An organization has decided on a cloudhub migration strategy that aims to minimize the organizations own IT resources. Currently, the organizational has all of its Mule applications running on its own premises and uses an premises load balancer that exposes all APIs under the base URL https://api.acme.com

As part of the migration strategy, the organization plans to migrate all of its Mule applications and load balancer to cloudhub
What is the most straight-forward and cost effective approach to the Mule applications deployment and load balancing that preserves the public URLs?

  1. Deploy the Mule applications to Cloudhub
    Update the CNAME record for an api.acme.com in the organizations DNS server pointing to the A record of a cloudhub dedicated load balancer(DLB)
    Apply mapping rules in the DLB to map URLs to their corresponding Mule applications
  2. For each migrated Mule application, deploy an API proxy Mule application to Cloudhub with all applications under the control of a dedicated load balancer(CLB) Update the CNAME record for api.acme.com in the organization DNS server pointing to the A record of a cloudhub dedicated load balancer(DLB)
    Apply mapping rules in the DLB to map each API proxy application to its corresponding Mule applications
  3. Deploy the Mule applications to Cloudhub
    Create CNAME record for api.acme.com in the Cloudhub Shared load balancer (SLB) pointing to the A record of the on-premise load balancer
    Apply mapping rules in the SLB to map URLs to their corresponding Mule applications
  4. Deploy the Mule applications to Cloudhub
    Update the CNAME record for api.acme.com in the organization DNS server pointing to the A record of the cloudhub shared load balancer(SLB)
    Apply mapping rules in the SLB to map URLs to their corresponding Mule applications.

Answer(s): A

Explanation:

https://help.mulesoft.com/s/feed/0D52T000055pzgsSAA.



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.

  1. VM
  2. Anypoint MQ
  3. SFTP
  4. ObjectStore

Answer(s): A

Explanation:

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:



A mule application uses an HTTP request operation to involve an external API. The external API follows the HTTP specification for proper status code usage.
What is possible cause when a 3xx status code is returned to the HTTP Request operation from the external API?

  1. The request was not accepted by the external API
  2. The request was Redirected to a different URL by the external API
  3. The request was NOT RECEIVED by the external API
  4. The request was ACCEPTED by the external API

Answer(s): B

Explanation:

3xx HTTP status codes indicate a redirection that the user agent (a web browser or a crawler) needs to take further action when trying to access a particular resource.


Reference:

https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html



Viewing page 16 of 56
Viewing questions 76 - 80 out of 273 questions


Post your Comments and Discuss Salesforce MuleSoft-Integration-Architect-I exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!