Mulesoft MCIA-LEVEL1 Online Practice Questions and Exam Preparation

Mulesoft MCIA-LEVEL1 Online Questions & Answers

• Question 261:

  A Mule application contains a Batch Job with two Batch Steps (Batch_Step_l and Batch_Step_2). A payload with 1000 records is received by the Batch Job.

  How many threads are used by the Batch Job to process records, and how does each Batch Step process records within the Batch Job?

  A. Each Batch Job uses SEVERAL THREADS for the Batch Steps Each Batch Step instance receives ONE record at a time as the payload, and RECORDS are processed IN PARALLEL within and between the two Batch Steps
  B. Each Batch Job uses a SINGLE THREAD for all Batch steps Each Batch step instance receives ONE record at a time as the payload, and RECORDS are processed IN ORDER, first through Batch_Step_l and then through Batch_Step_2
  C. Each Batch Job uses a SINGLE THREAD to process a configured block size of record Each Batch Step instance receives A BLOCK OF records as the payload, and BLOCKS of records are processed IN ORDER
  D. Each Batch Job uses SEVERAL THREADS for the Batch Steps Each Batch Step instance receives ONE record at a time as the payload, and BATCH STEP INSTANCES execute IN PARALLEL to process records and Batch Steps in ANY order as fast as possible
  A. Each Batch Job uses SEVERAL THREADS for the Batch Steps Each Batch Step instance receives ONE record at a time as the payload, and RECORDS are processed IN PARALLEL within and between the two Batch Steps

  ---

  # Each Batch Job uses SEVERAL THREADS for the Batch Steps

  # Each Batch Step instance receives ONE record at a time as the payload. It's not received in a block, as it does not wait for multiple records to be completed before moving to next batch step. (So Option D is out of choice)

  # RECORDS are processed IN PARALLEL within and between the two Batch Steps.

  # RECORDS are not processed in order. Let's say if second record completes batch_step_1 before record 1, then it moves to batch_step_2 before record 1. (So option C and D are out of choice)

  # A batch job is the scope element in an application in which Mule processes a message payload as a batch of records. The term batch job is inclusive of all three phases of processing: Load and Dispatch, Process, and On Complete.

  # A batch job instance is an occurrence in a Mule application whenever a Mule flow executes a batch job. Mule creates the batch job instance in the Load and Dispatch phase. Every batch job instance is identified internally using a unique String known as batch job instance id.

  

• Question 262:

  Refer to the exhibit.

  

  A Mule application is deployed to a multi-node Mule runtime cluster. The Mule application uses the competing consumer pattern among its cluster replicas to receive JMS messages from a JMS queue. To process each received JMS message, the following steps are performed in a flow:

  Step l: The JMS Correlation ID header is read from the received JMS message.

  Step 2: The Mule application invokes an idempotent SOAP webservice over HTTPS, passing the JMS Correlation ID as one parameter in the SOAP request.

  Step 3: The response from the SOAP webservice also returns the same JMS Correlation ID.

  Step 4: The JMS Correlation ID received from the SOAP webservice is validated to be identical to the JMS Correlation ID received in Step 1.

  Step 5: The Mule application creates a response JMS message, setting the JMS Correlation ID message header to the validated JMS Correlation ID and publishes that message to a response JMS queue.

  Where should the Mule application store the JMS Correlation ID values received in Step 1 and Step 3 so that the validation in Step 4 can be performed, while also making the overall Mule application highly available, fault-tolerant, performant, and maintainable?

  A. Both Correlation ID values should be stored in a persistent object store
  B. Both Correlation ID values should be stored In a non-persistent object store
  C. The Correlation ID value in Step 1 should be stored in a persistent object store The Correlation ID value in step 3 should be stored as a Mule event variable/attribute
  D. Both Correlation ID values should be stored as Mule event variable/attribute
  C. The Correlation ID value in Step 1 should be stored in a persistent object store The Correlation ID value in step 3 should be stored as a Mule event variable/attribute

  ---

  # If we store Correlation id value in step 1 as Mule event variables/attributes, the values will be cleared after server restart and we want system to be fault tolerant.

  # The Correlation ID value in Step 1 should be stored in a persistent object store.

  # We don't need to store Correlation ID value in Step 3 to persistent object store. We can store it but as we also need to make application performant. We can avoid this step of accessing persistent object store.

  # Accessing persistent object stores slow down the performance as persistent object stores are by default stored in shared file systems.

  # As the SOAP service is idempotent in nature. In case of any failures , using this Correlation ID saved in first step we can make call to SOAP service and validate the Correlation ID.

  Top of Form

  Additional Information:

  # Competing Consumers are multiple consumers that are all created to receive messages from a single Point-to-Point Channel. When the channel delivers a message, any of the consumers could potentially receive it. The messaging system's implementation determines which consumer actually receives the message, but in effect the consumers compete with each other to be the receiver. Once a consumer receives a message, it can delegate to the rest of its application to help process the message.

  # In case you are unaware about term idempotent re is more info:

  Idempotent operations means their result will always same no matter how many times these operations are invoked.

  

  

• Question 263:

  An organization's governance process requires project teams to get formal approval from all key stakeholders for all new Integration design specifications. An integration Mule application Is being designed that interacts with various backend systems. The Mule application will be created using Anypoint Design Center or Anypoint Studio and will then be deployed to a customer-hosted runtime. What key elements should be included in the integration design specification when requesting approval for this Mule application?

  A. SLAs and non-functional requirements to access the backend systems
  B. Snapshots of the Mule application's flows, including their error handling
  C. A list of current and future consumers of the Mule application and their contact details
  D. The credentials to access the backend systems and contact details for the administrator of each system
  A. SLAs and non-functional requirements to access the backend systems

  ---

  SLAs and non-functional requirements to access the backend systems. Only this option actually speaks to design parameters and reqs. # Below two are technical implementations and not the part of design: - Snapshots of the Mule application's flows, including their error handling - The credentials to access the backend systems and contact details for the administrator of each system # List of consumers is not relevant to the design

• Question 264:

  Anypoint Exchange is required to maintain the source code of some of the assets committed to it, such as Connectors, Templates, and API specifications. What is the best way to use an organization's source-code management (SCM) system in this context?

  A. Organizations should continue to use an SCM system of their choice, in addition to keeping source code for these asset types in Anypoint Exchange, thereby enabling parallel development, branching, and merging
  B. Organizations need to use Anypoint Exchange as the main SCM system to centralize versioning and avoid code duplication
  C. Organizations can continue to use an SCM system of their choice for branching and merging, as long as they follow the branching and merging strategy enforced by Anypoint Exchange
  D. Organizations need to point Anypoint Exchange to their SCM system so Anypoint Exchange can pull source code when requested by developers and provide it to Anypoint Studio
  B. Organizations need to use Anypoint Exchange as the main SCM system to centralize versioning and avoid code duplication

  ---

  # Organization should continue to use SCM system of their choice, in addition to keeping source code for these asset types in Anypoint Exchange, thereby enabling parallel development, branching.

  # Reason is that Anypoint exchange is not full fledged version repositories like GitHub.

  # But at same time it is tightly coupled with Mule assets

• Question 265:

  A mule application designed to fulfil two requirements

  A. Use Cloud hub persistent queues for FTPS files processing There is no need to configure VM queues for the batch jobs scope as it uses by default the worker's disc for VM queueing
  B. Use Cloud hub persistent VM queue for FTPS file processing There is no need to configure VM queues for the batch jobs scope as it uses by default the worker's JVM memory for VM queueing
  C. Use Cloud hub persistent VM queues for FTPS file processing Disable VM queue for the batch job scope
  D. Use VM connector persistent queues for FTPS file processing Disable VM queue for the batch job scope
  C. Use Cloud hub persistent VM queues for FTPS file processing Disable VM queue for the batch job scope

• Question 266:

  An organization uses one specific CloudHub (AWS) region for all CloudHub deployments. How are CloudHub workers assigned to availability zones (AZs) when the organization's Mule applications are deployed to CloudHub in that region?

  A. Workers belonging to a given environment are assigned to the same AZ within that region.
  B. AZs are selected as part of the Mule application's deployment configuration.
  C. Workers are randomly distributed across available AZs within that region.
  D. An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ
  C. Workers are randomly distributed across available AZs within that region.

  ---

  Correct answer is Workers are randomly distributed across available AZs within that region. This ensure high availability for deployed mule applications Mulesoft documentation

  reference : https://docs.mulesoft.com/runtime-manager/cloudhub-hadr

• Question 267:

  An API has been unit tested and is ready for integration testing. The API is governed by a Client ID Enforcement policy in all environments.

  What must the testing team do before they can start integration testing the API in the Staging environment?

  A. They must access the API portal and create an API notebook using the Client ID and Client Secret supplied by the API portal in the Staging environment
  B. They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API
  C. They must be assigned as an API version owner of the API in the Staging environment
  D. They must request access to the Staging environment and obtain the Client ID and Client Secret for that environment to be used for testing the API
  B. They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API

  ---

  # It's mentioned that the API is governed by a Client ID Enforcement policy in all environments.

  # Client ID Enforcement policy allows only authorized applications to access the deployed API implementation.

  # Each authorized application is configured with credentials: client_id and client_secret.

  # At runtime, authorized applications provide the credentials with each request to the API implementation. MuleSoft

  https://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-policies

• Question 268:

  An application deployed to a runtime fabric environment with two cluster replicas is designed to periodically trigger of flow for processing a high-volume set of records from the source system and synchronize with the SaaS system using the Batch job scope.

  After processing 1000 records in a periodic synchronization of 1 lakh records, the replicas in which batch job instance was started went down due to unexpected failure in the runtime fabric environment

  What is the consequence of losing the replicas that run the Batch job instance?

  A. The remaining 99000 records will be lost and left and processed
  B. The second replicas will take over processing the remaining 99000 records
  C. A new replacement replica will be available and will be process all 1,00,000 records from scratch leading to duplicate record processing
  D. A new placement replica will be available and will take or processing the remaining 99,000 records
  D. A new placement replica will be available and will take or processing the remaining 99,000 records

  ---

  When a batch job instance running on a runtime fabric environment with two cluster replicas encounters an unexpected failure, the following sequence of events occurs:

  Failure Detection: The runtime fabric environment detects the failure of the replica running the batch job.

  Replica Replacement: A new replica is provisioned to replace the failed one.

  Batch Job State Recovery: MuleSoft's batch processing mechanism ensures that the state of the batch job is periodically saved (checkpointing). This allows the new replica to resume processing from the last saved state.

  Resumption of Processing: The new replica takes over the batch job, continuing from where the previous one left off, thus processing the remaining 99,000 records without starting from scratch or causing duplicate processing.

  References: MuleSoft Documentation on Batch Processing Runtime Fabric Guide

• Question 269:

  An organization has strict unit test requirement that mandate every mule application must have an MUnit test suit with a test case defined for each flow and a minimum test coverage of 80%.

  A developer is building Munit test suit for a newly developed mule application that sends API request to an external rest API.

  What is the effective approach for successfully executing the Munit tests of this new application while still achieving the required test coverage for the Munit tests?

  A. Invoke the external endpoint of the rest API from the mule floors
  B. Mark the rest API invocations in the Munits and then call the mocking service flow that simulates standard responses from the REST API
  C. Mock the rest API invocation in the Munits and return a mock response for those invocations
  D. Create a mocking service flow to simulate standard responses from the rest API and then configure the mule flows to call the marking service flow
  C. Mock the rest API invocation in the Munits and return a mock response for those invocations

• Question 270:

  What requires configuration of both a key store and a trust store for an HTTP Listener?

  A. Support for TLS mutual (two-way) authentication with HTTP clients
  B. Encryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and https://customer.com/api)
  C. Encryption of both HTTP request and HTTP response bodies for all HTTP clients
  D. Encryption of both HTTP request header and HTTP request body for all HTTP clients
  A. Support for TLS mutual (two-way) authentication with HTTP clients

  ---

  1 way SSL : The server presents its certificate to the client and the client adds it to its list of trusted certificate. And so, the client can talk to the server. 2-way SSL: The same principle but both ways. i.e. both the client and the server has to establish trust between themselves using a trusted certificate. In this way of a digital handshake, the server needs to present a certificate to authenticate itself to client and client has to present its certificate to server.

  # TLS is a cryptographic protocol that provides communications security for your Mule app.

  # TLS offers many different ways of exchanging keys for authentication, encrypting data, and guaranteeing message integrity Keystores and Truststores Truststore and keystore contents differ depending on whether they are used for clients or servers:

  For servers: the truststore contains certificates of the trusted clients, the keystore contains the private and public key of the server. For clients: the truststore contains certificates of the trusted servers, the keystore contains the private and public key of the client. Adding both a keystore and a truststore to the configuration implements two-way TLS authentication also known as mutual authentication.

  # in this case, correct answer is Support for TLS mutual (two-way) authentication with HTTP clients.