Salesforce Certified MuleSoft Platform Integration Architect

Salesforce Certified MuleSoft Platform Integration Architect practice questions, page 2 of 3, with answer review and explanations.

Question 6

A marketing organization is designing a Mule application to process campaign data. The Mule application will periodically check for a file in an SFTP location and process the records in the file. The size of the file can vary from 10MB to 5GB. Due to the limited availability of vCores, the Mule application is deployed to a single CloudHub worker/replica configured with vCore size 0.2. The application must transform and send different formats of this file to three different downstream SFTP locations. What is the most direct way to configure the SFTP operations or event sources to process the large files to support these deployment requirements?

  1. Use a file-stored repeatable stream
  2. Use a file-stored nonrepeatable stream
  3. Use an in-memory repeatable stream
  4. Use an in-memory nonrepeatable stream

Question 7

A new Mule application has been deployed through Runtime Manager to CloudHub 1.0 using a CI/CD pipeline with sensitive properties set as cleartext. The Runtime Manager Administrator opened a high priority incident ticket about this violation of their security requirements indicating these sensitive properties values must not be stored or visible in Runtime Manager but should be changeable in Runtime Manager by Administrators with proper permissions. How can the Mule application be deployed while safely hiding the sensitive properties?

  1. Add encrypted versions of the sensitive properties as global configuration properties in the Mule application
  2. Add a new wrapper.java.additional.XX parameter for each sensitive property in the wrapper.conf file used by the CI/CD pipeline scripts
  3. Create a variable for each sensitive property and declare them as hidden in the CI/CD pipeline scripts
  4. Add an ArrayList of all the sensitive properties' names in the mule-artifact.json file of the application

Question 8

An organization has built a large monolithic application over the years and is currently looking to transition to a microservices architecture. During this transition phase, it has built some System APIs as Mule applications that provide access to different pieces of functionality of the monolithic application. The System APIs are deployed to Mule runtimes in a customer-hosted EC2 instance in AWS. The System APIs communicate directly with one database used by the monolithic application. Currently, a Database connector and configuration for that connector must be built into every project. There is a plan to partition this database into various smaller data stores in the future. What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?

  1. Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically
  2. Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy
  3. Build another System API that connects to the database, and refactor all the other APIs to make requests through the new System API to access the database
  4. Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API

Question 9

An architect is designing a Mule application to meet the following two requirements: 1. The application must process files asynchronously and reliably from an FTPS server to a back-end database using VM intermediary queues for load-balancing Mule events. 2. The application must process a medium rate of records from a source to a target system using a Batch Job scope. To make the Mule application more reliable, the Mule application will be deployed to two CloudHub 1.0 workers. Following MuleSoft-recommended best practices, how should the Mule application deployment typically be configured in Runtime Manger to best support the performance and reliability goals of both the Batch Job scope and the file processing VM queues?

  1. In the Runtime Manager Properties tab, enable persistent VM queues for the FTPS connector
  2. Check the Non-persistent VM queues checkbox in the application deployment configuration
  3. In the Runtime Manager Properties tab, disable persistent VM queues for Batch Job scopes
  4. Check the Persistent VM queues checkbox in the application deployment configuration

Question 10

Refer to the exhibit. A customer is running Mule applications on Runtime Fabric for Self-Managed Kubernetes (RTF-BYOK8) in a multi-cloud environment. Based on this configuration, how do Agents and Runtime Manager communicate, and what is exchanged between them?

  1. Agents communicate with Runtime Manager to provide updates on cluster status, download images, and update Mule applications (automatically when available) from the container registry
  2. Agents communicate with Runtime Manager to provide updates on cluster status, download images, and update Mule applications (when available and chosen to do so by customer) from the container registry
  3. Runtime Manager initiates traffic to Agents to check the status of clusters and auto-deploys new images when updates to Mule applications are available
  4. Runtime Manager communicates with Agents to provide updates on cluster status, download images, and update Mule applications (when available and chosen to do so by customer) from the container registry