CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. MuleSoft
  5. MCIA-LEVEL-1

Free MCIA-LEVEL-1 Exam Braindumps (page: 19)

Page 19 of 62
PDF with 244 Questions

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


Reference:

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



An organization is migrating all its Mule applications to Runtime Fabric (RTF). None of the Mule applications use Mule domain projects.
Currently, all the Mule applications have been manually deployed to a server group among several customer hosted Mule runtimes.
Port conflicts between these Mule application deployments are currently managed by the DevOps team who carefully manage Mule application properties files.
When the Mule applications are migrated from the current customer-hosted server group to Runtime Fabric (RTF), fo the Mule applications need to be rewritten and what DevOps port configuration responsibilities change or stay the same?

  1. Yes, the Mule applications Must be rewritten DevOps No Longer needs to manage port conflicts between the Mule applications
  2. Yes, the Mule applications Must be rewritten DevOps Must Still Manage port conflicts.
  3. NO, The Mule applications do NOT need to be rewritten DevOps MUST STILL manage port conflicts
  4. NO, the Mule applications do NO need to be rewritten DevOps NO LONGER needs to manage port conflicts between the Mule applications.

Answer(s): C

Explanation:

* Anypoint Runtime Fabric is a container service that automates the deployment and orchestration of your Mule applications and gateways.
* Runtime Fabric runs on customer-managed infrastructure on AWS, Azure, virtual machines (VMs) or bare-metal servers.
* As none of the Mule applications use Mule domain projects. applications are not required to be rewritten. Also when applications are deployed on RTF, by default ingress is allowed only on 8081.
* Hence port conflicts are not required to be managed by DevOps team



Page 19 of 62



Post your Comments and Discuss MuleSoft MCIA-LEVEL-1 exam with other Community members:

sanath sekar commented on September 05, 2024
nice good good expirence with these dumps provided
Anonymous
upvote