Mulesoft MCIA-LEVEL1 Online Practice Questions and Exam Preparation

Mulesoft MCIA-LEVEL1 Online Questions & Answers

• Question 231:

  An integration Mute application consumes and processes a list of rows from a CSV file. Each row must be read from the CSV file, validated, and the row data sent to a JMS queue, in the exact order as in the CSV file.

  If any processing step for a row falls, then a log entry must be written for that row, but processing of other rows must not be affected.

  What combination of Mute components is most idiomatic (used according to their intended purpose) when Implementing the above requirements?

  A. Scatter-Gather component On Error Continue scope
  B. VM connector first Successful scope On Error Propagate scope
  C. For Each scope On Error Continue scope
  D. Async scope On Error Propagate scope
  C. For Each scope On Error Continue scope

  ---

  # On Error Propagate halts execution and sends error to the client. In this scenario it's mentioned that "processing of other rows must not be affected" so Option B and C are ruled out.

  # Scatter gather is used to club multiple responses together before processing. In this scenario, we need sequential processing. So option A is out of choice.

  # Correct answer is For Each scope and On Error Continue scope Below requirement can be fulfilled in the below way 1) Using For Each scope , which will send each row from csv file sequentially. each row needs to be sent sequentially as requirement is to send the message in exactly the same way as it is mentioned in the csv file 2) Also other part of requirement is if any processing step for a row fails then it should log an error but should not affect other record processing . This can be achieved using On error Continue scope on these set of activities. so that error will not halt the processing. Also logger needs to be added in error handling section so that it can be logged.

  # Attaching diagram for reference. Here it's try scope, but similar would be the case with For Each loop.

  

• Question 232:

  Refer to the exhibit.

  

  A business process involves the receipt of a file from an external vendor over SFTP. The file needs to be parsed and its content processed, validated, and ultimately persisted to a database. The delivery mechanism is expected to change in the future as more vendors send similar files using other mechanisms such as file transfer or HTTP POST.

  What is the most effective way to design for these requirements in order to minimize the impact of future change?

  A. Use a MuleSoft Scatter-Gather and a MuleSoft Batch Job to handle the different files coming from different sources
  B. Create a Process API to receive the file and process it using a MuleSoft Batch Job while delegating the data save process to a System API
  C. Create an API that receives the file and invokes a Process API with the data contained In the file, then have the Process API process the data using a MuleSoft Batch Job and other System APIs as needed
  D. Use a composite data source so files can be retrieved from various sources and delivered to a MuleSoft Batch Job for processing
  C. Create an API that receives the file and invokes a Process API with the data contained In the file, then have the Process API process the data using a MuleSoft Batch Job and other System APIs as needed

  ---

  # Scatter-Gather is used for parallel processing, to improve performance. In this scenario, input files are coming from different vendors so mostly at different times. Goal here is to minimize the impact of future change. So scatter Gather is not the correct choice.

  # If we use 1 API to receive all files from different Vendors, any new vendor addition will need changes to that 1 API to accommodate new requirements. So Option A and C are also ruled out.

  # Correct answer is Create an API that receives the file and invokes a Process API with the data contained in the file, then have the Process API process the data using a MuleSoft Batch Job and other System APIs as needed. Answer to this question lies in the API led connectivity approach.

  # API-led connectivity is a methodical way to connect data to applications through a series of reusable and purposeful modern APIs that are each developed to play a specific role ?unlock data from systems, compose data into processes, or deliver an experience. System API : System API tier, which provides consistent, managed, and secure access to backend systems. Process APIs : Process APIs take core assets and combines them with some business logic to create a higher level of value. Experience APIs : These are designed specifically for consumption by a specific end-user app or device. So in case of any future plans , organization can only add experience API on addition of new Vendors, which reuse the already existing process API. It will keep impact minimal.

  

• Question 233:

  Which Exchange asset type represents a complete API specification in RAML or OAS format?

  A. Connectors
  B. REST APIs
  C. API Spec Fragments
  D. SOAP APIs
  B. REST APIs

• Question 234:

  A developer is examining the responses from a RESTful web service that is compliant with the Mypertext Transfer Protocol (HTTP/1.1) a8 defined by the Internet Engineering Task Force (IETF).

  In this HTTP/1.1-compliant web service, which class of HTTP response status codes should be specified to indicate when client requests are successfully received, understood, and accepted by the web service?

  A. 3xx
  B. 2xx
  C. 4xx
  D. 5xx
  B. 2xx

• Question 235:

  What aspect of logging is only possible for Mule applications deployed to customer-hosted Mule runtimes, but NOT for Mule applications deployed to CloudHub?

  A. To send Mule application log entries to Splunk
  B. To change tog4j2 tog levels in Anypoint Runtime Manager without having to restart the Mule application
  C. To log certain messages to a custom log category
  D. To directly reference one shared and customized log4j2.xml file from multiple Mule applications
  D. To directly reference one shared and customized log4j2.xml file from multiple Mule applications

  ---

  # Correct answer is To directly reference one shared and customized log4j2.xml file from multiple Mule applications. Key word to note in the answer is directly.

  # By default, CloudHub replaces a Mule application's log4j2.xml file with a CloudHub log4j2.xml file. This specifies the CloudHub appender to write logs to the CloudHub logging service.

  # You cannot modify CloudHub log4j2.xml file to add any custom appender. But there is a process in order to achieve this. You need to raise a request on support portal to disable CloudHub provided Mule application log4j2 file.

  # Once this is done , Mule application's log4j2.xml file is used which you can use to send/export application logs to other log4j2 appenders, such as a custom logging system MuleSoft does not own any responsibility for lost logging data due to misconfiguration of your own log4j appender if it happens by any chance.

  # One more difference between customer-hosted Mule runtimes and CloudHub deployed mule instance is that

  

  

  -

  CloudHub system log messages cannot be sent to external log management system without installing custom CH logging configuration through support

  -

  where as Customer-hosted runtime can send system and application log to external log management system MuleSoft

  https://docs.mulesoft.com/runtime-manager/viewing-log-data https://docs.mulesoft.com/runtime-manager/custom-log-appender

• Question 236:

  An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API's public portal. The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

  A. The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run.
  B. The API producer should be contacted to understand the change to existing functionality.
  C. The API producer should be requested to run the old version in parallel with the new one.
  D. The API client code ONLY needs to be changed if it needs to take advantage of new features.
  D. The API client code ONLY needs to be changed if it needs to take advantage of new features.

  ---

  # Semantic Versioning is a 3-component number in the format of X.Y.Z, where :

  X stands for a major version.

  Y stands for a minor version:

  Z stands for a patch.

  So, SemVer is of the form Major.Minor.Patch Coming to our question , minor version of the API has been changed which is backward compatible. Hence there is no change required on API client end. If they want to make use of new featured that have been added as a part of minor version change they may need to change code at their end. Hence correct answer is The API client code ONLY needs to be changed if it needs to take advantage of new features.

  

• Question 237:

  Which component is responsible for collecting and visualizing metrics such as CPU and memory usage for Mule applications?

  A. Anypoint Exchange
  B. API Manager
  C. Anypoint Monitoring
  D. Anypoint CLI
  C. Anypoint Monitoring

  ---

  Anypoint Monitoring provides visibility into application and runtime metrics, enabling performance analysis and alerting.

• Question 238:

  A leading e-commerce giant will use Mulesoft API's on runtime fabric (RTF) to process customer orders. Some customer's sensitive information such as credit card information is also there as a part of a API payload. What approach minimizes the risk of matching sensitive data to the original and can convert back to the original value whenever and wherever required?

  A. Apply masking to hide the sensitive information and then use API
  B. manager to detokenize the masking format to return the original value
  C. create a tokenization format and apply a tokenization policy to the API Gateway
  D. Used both masking and tokenization
  E. Apply a field level encryption policy in the API Gateway
  C. create a tokenization format and apply a tokenization policy to the API Gateway

  ---

  To minimize the risk of exposing sensitive data such as credit card information while still allowing it to be converted back to its original value when necessary, tokenization is the most effective approach. Tokenization replaces sensitive data with a non-sensitive equivalent, called a token, which has no exploitable value. This method ensures that the original sensitive data is stored securely and only accessible through a secure tokenization system.

  In this scenario, applying a tokenization policy at the API Gateway ensures that sensitive information is replaced with tokens before the data leaves the trusted boundary. This minimizes the risk of matching sensitive data to the original. When the original data is needed, the tokenization system can detokenize the token back to its original value securely.

  References: MuleSoft Documentation on Tokenization

• Question 239:

  An organization's IT team follows an API-led connectivity approach and must use Anypoint Platform to implement a System AP\ that securely accesses customer data. The organization uses Salesforce as the system of record for all customer data, and its most important objective is to reduce the overall development time to release the System API. The team's integration architect has identified four different approaches to access the customer data from within the implementation of the System API by using different Anypoint Connectors that all meet the technical requirements of the project.

  A. Use the Anypoint Connector for Database to connect to a MySQL database to access a copy of the customer data
  B. Use the Anypoint Connector for HTTP to connect to the Salesforce APIs to directly access the customer data
  C. Use the Anypoint Connector for Salesforce to connect to the Salesforce APIs to directly access the customer data
  D. Use the Anypoint Connector tor FTP to download a file containing a recent near-real time extract of the customer data
  C. Use the Anypoint Connector for Salesforce to connect to the Salesforce APIs to directly access the customer data

• Question 240:

  According to MuteSoft, which principle is common to both Service Oriented Architecture (SOA) and API-led connectivity approaches?

  A. Service centralization
  B. Service statefulness
  C. Service reusability
  D. Service interdependence
  C. Service reusability