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-MAINTENANCE

Free MCIA-LEVEL-1-MAINTENANCE Exam Braindumps (page: 14)

Page 13 of 30
PDF with 116 Questions

An organization has an HTTPS-enabled Mule application named Orders API that receives requests from another Mule application named Process Orders.

The communication between these two Mule applications must be secured by TLS mutual

authentication (two-way TLS).

At a minimum, what must be stored in each truststore and keystore of these two Mule applications to properly support two-way TLS between the two Mule applications while properly protecting each Mule application's keys?

  1. Orders API truststore: The Orders API public key
    Process Orders keystore: The Process Orders private key and public key
  2. Orders API truststore: The Orders API private key and public key Process Orders keystore: The Process Orders private key public key
  3. Orders API truststore: The Process Orders public key
    Orders API keystore: The Orders API private key and public key

    Process Orders truststore: The Orders API public key
    Process Orders keystore: The Process Orders private key and public key
  4. Orders API truststore: The Process Orders public key
    Orders API keystore: The Orders API private key
    Process Orders truststore: The Orders API public key
    Process Orders keystore: The Process Orders private key

Answer(s): C

Explanation:


Reference:

https://www.caeliusconsulting.com/blogs/one-way-and-two-way-tls-and-their
implementation-in-mulesoft/



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 that participates in the local transaction.

What is the behavior of the Scatter-Gather when running within this local transaction?

  1. Execution of each route within the Scatter-Gather occurs sequentially Any error that occurs inside the Scatter-Gather will result in a rollback of all the database operations
  2. Execution of all routes within the Scatter-Gather occurs in parallel Any error that occurs inside the Scatter-Gather will result in a rollback of all the database operations
  3. Execution of each route within the Scatter-Gather occurs sequentially Any error that occurs inside the Scatter-Gather will NOT result in a rollback of any of the database operations
  4. Execution of each route within the Scatter-Gather occurs in parallel Any error that occurs inside the Scatter-Gather will NOT result in a rollback of any of the database operations

Answer(s): A

Explanation:


Reference:

https://docs.mulesoft.com/mule-runtime/4.4/transaction-management



An organization is creating a Mule application that will be deployed to CloudHub. The Mule application has a property named dbPassword that stores a database user's password.

The organization's security standards indicate that the dbPassword property must be hidden from every Anypoint Platform user after the value is set in the Runtime Manager Properties tab.

What configuration in the Mule application helps hide the dbPassword property value in Runtime Manager?

  1. Use secure::dbPassword as the property placeholder name and store the cleartext (unencrypted) value in a secure properties placeholder file
  2. Use secure::dbPassword as the property placeholder name and store the property encrypted value in a secure properties placeholder file
  3. Add the dbPassword property to the secureProperties section of the pom.xml file
  4. Add the dbPassword property to the secureProperties section of the mule-artifact.json file

Answer(s): B

Explanation:


Reference:

https://docs.mulesoft.com/runtime-manager/secure-application-properties



An organization is designing a Mule application to periodically poll an SFTP location for new files containing sales order records and then process those sales orders. Each sales order must be processed exactly once.

To support this requirement, the Mule application must identify and filter duplicate sales orders on the basis of a unique ID contained in each sales order record and then only send the new sales orders to the downstream system.

What is the most idiomatic (used for its intended purpose) Anypoint connector, validator, or scope that can be configured in the Mule application to filter duplicate sales orders on the basis of the unique ID field contained in each sales order record?

  1. Configure a Cache scope to filter and store each record from the received file by the order ID
  2. Configure a Database connector to filter and store each record by the order ID
  3. Configure an Idempotent Message Validator component to filter each record by the order ID
  4. Configure a watermark In an On New or Updated File event source to filter unique records by the order ID

Answer(s): C

Explanation:


Reference:

https://docs.mulesoft.com/mule-runtime/3.9/idempotent-filter






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

MCIA-LEVEL-1-MAINTENANCE Discussions & Posts