Mulesoft MCIA-LEVEL1 Online Practice Questions and Exam Preparation

Mulesoft MCIA-LEVEL1 Online Questions & Answers

• Question 61:

  A company is planning to extend its Mule APIs to the Europe region. Currently all new applications are deployed to Cloudhub in the US region following this naming convention

  {API name}-{environment}. for example, Orders-SAPI-dev, Orders-SAPI-prod etc.

  Considering there is no network restriction to block communications between API's, what strategy should be implemented in order to apply the same new API's running in the EU region of CloudHub as well to minimize latency between API's and target users and systems in Europe?

  A. Set region property to Europe (eu-de) in API manager for all the mule application No need to change the naming convention
  B. Set region property to Europe (eu-de) in API manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users
  C. Set region property to Europe (eu-de) in runtime manager for all the mule application No need to change the naming convention
  D. Set region property to Europe (eu-de) in runtime manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users
  D. Set region property to Europe (eu-de) in runtime manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users

• Question 62:

  The company's FTPS server login username and password

  A. TLS context trust store containing a public certificate for the company. The company's PGP public key that was used to sign the files
  B. The partner's PGP public key used by the company to login to the FTPS server. A TLS context key store containing the private key for the company The partner's PGP private key that was used to sign the files
  C. The company's FTPS server login username and password. A TLS context trust store containing a public certificate for ftps.partner.com The partner's PGP public key that was used to sign the files
  D. The partner's PGP public key used by the company to login to the FTPS server. A TLS context key store containing the private key for ftps.partner.com The company's PGP private key that was used to sign the files
  C. The company's FTPS server login username and password. A TLS context trust store containing a public certificate for ftps.partner.com The partner's PGP public key that was used to sign the files

  ---

  When configuring secure communication with an FTPS server and handling signed files, the necessary components include:

  FTPS Server Login Credentials: The username and password used to authenticate with the company's FTPS server.

  TLS Context Trust Store: This should contain the public certificate for the FTPS server (ftps.partner.com) to establish a secure SSL/TLS connection.

  Partner's PGP Public Key: This is used to verify the signature of the files received from the partner, ensuring data integrity and authenticity.

  These components collectively ensure secure communication and data validation.

  References: MuleSoft Documentation on FTPS and PGP Encryption Best Practices for Secure File Transfer and Encryption

• Question 63:

  As a part of project requirement, client will send a stream of data to mule application. Payload size can vary between 10mb to 5GB. Mule application is required to transform the data and send across multiple sftp servers. Due to the cost cuttings in the organization, mule application can only be allocated one worker with size of 0.2 vCore. As an integration architect , which streaming strategy you would suggest to handle this scenario?

  A. In-memory non repeatable stream
  B. File based non-repeatable stream
  C. In-memory repeatable stream
  D. File based repeatable storage
  D. File based repeatable storage

  ---

  As the question says that data needs to be sent across multiple sftp serves , we cannot use non-repeatable streams. The non-repeatable strategy disables repeatable streams, which enables you to read an input stream only once.

  You cant use in memory storage because with 0.2 vcore you will get only 1 GB of heap memory. Hence application will error out for file more than 1 GB.

  Hence the correct option is file base repeatable stream

• Question 64:

  An insurance company is implementing a MuleSoft API to get inventory details from the two vendors. Due to network issues, the invocations to vendor applications are getting timed- out intermittently. But the transactions are successful upon reprocessing

  What is the most performant way of implementing this requirement?

  A. Implement a scatter-gather scope to invoke the two vendor applications on two different route Use the Until-Successful scope to implement the retry mechanism for timeout errors on each route
  B. Implement a Choice scope to invoke the two vendor applications on two different route Use the try-catch scope to implement the retry mechanism for timeout errors on each route
  C. Implement a For-Each scope to invoke the two vendor applications Use until successful scope to implement the retry mechanism for the timeout errors
  D. Implement Round-Robin scope to invoke the two vendor applications on two different routes Use the Try-Catch scope to implement retry mechanism for timeout errors on each route
  A. Implement a scatter-gather scope to invoke the two vendor applications on two different route Use the Until-Successful scope to implement the retry mechanism for timeout errors on each route

• Question 65:

  A stock broking company makes use of CloudHub VPC to deploy Mule applications. Mule application needs to connect to a database application in the customers on-premises corporate data center and also to a Kafka cluster running in AWS VPC. How is access enabled for the API to connect to the database application and Kafka cluster securely?

  A. Set up a transit gateway to the customers on-premises corporate datacenter to AWS VPC
  B. Setup AnyPoint VPN to the customer's on-premise corporate data center and VPC peering with AWS VPC
  C. Setup VPC peering with AWS VPC and the customers devices corporate data center
  D. Setup VPC peering with the customers onto my service corporate data center and Anypoint VPN to AWS VPC
  B. Setup AnyPoint VPN to the customer's on-premise corporate data center and VPC peering with AWS VPC

• Question 66:

  An Order microservice and a Fulfillment microservice are being designed to communicate with their dients through message-based integration (and NOT through API invocations).

  The Order microservice publishes an Order message (a kind of command message) containing the details of an order to be fulfilled. The intention is that Order messages are only consumed by one Mute application, the Fulfillment microservice.

  The Fulfilment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilted message (a kind of event message). Each OrderFulfilted message can be consumed by any interested Mule application, and the Order microservice is one such Mute application.

  What is the most appropriate choice of message broker(s) and message destination(s) in this scenario?

  A. Order messages are sent to an Anypoint MQ exchange OrderFulfilled messages are sent to an Anypoint MQ queue Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the load of both microservices
  B. Order messages are sent to a JMS queue. OrderFulfilled messages are sent to a JMS topic Both microservices interact with the same JMS provider (message broker) instance, which must therefore scale to support the load of both microservices
  C. Order messages are sent directly to the Fulfillment microservices. OrderFulfilled messages are sent directly to the Order microservice The Order microservice interacts with one AMQP-compatible message broker and the Fulfillment microservice interacts with a different AMQP-compatible message broker, so that both message brokers can be chosen and scaled to best support the load of each microservice
  D. Order messages are sent to a JMS queue. OrderFulfilled messages are sent to a JMS topic The Order microservice interacts with one JMS provider (message broker) and the Fulfillment microservice interacts with a different JMS provider, so that both message brokers can be chosen and scaled to best support the load of each microservice
  B. Order messages are sent to a JMS queue. OrderFulfilled messages are sent to a JMS topic Both microservices interact with the same JMS provider (message broker) instance, which must therefore scale to support the load of both microservices

  ---

  # If you need to scale a JMS provider/ message broker, - add nodes to scale it horizontally or - add memory to scale it vertically # Cons of adding another JMS provider/ message broker: - adds cost. - adds complexity to use two JMS brokers - adds Operational overhead if we use two brokers, say, ActiveMQ and IBM MQ # So Two options that mention to use two brokers are not best choice. # It's mentioned that "The Fulfillment microservice consumes Order messages, fulfills the order described therein, and

  then publishes an OrderFulfilled message. Each OrderFulfilled message can be consumed by any interested Mule application." - When you publish a message on a topic, it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. - When you send a message on a queue, it will be received by exactly one consumer. # As we need multiple consumers to consume the message below option is not valid choice:

  "Order messages are sent to an Anypoint MQ exchange. OrderFulfilled messages are sent to an Anypoint MQ queue. Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the load of both microservices" # Order messages are only consumed by one Mule application, the Fulfillment microservice, so we will publish it on queue and OrderFulfilled message can be consumed by any interested Mule application so it need to be published on Topic using same

  broker. #

  Correct Answer:

  Best choice in this scenario is: "Order messages are sent to a JMS queue. OrderFulfilled messages are sent to a JMS topic. Both microservices interact with the same JMS provider (message broker) instance, which must therefore scale to support the load of both microservices" Tried to depict scenario in diagram:

  

• Question 67:

  What is maximum vCores can be allocated to application deployed to CloudHub?

  A. 1 vCores
  B. 2 vCores
  C. 4 vCores
  D. 16 vCores
  D. 16 vCores

• Question 68:

  A mule application is being designed to perform product orchestration. The Mule application needs to join together the responses from an inventory API and a Product Sales History API with the least latency. To minimize the overall latency. What is the most idiomatic (used for its intended purpose) design to call each API request in the Mule application?

  A. Call each API request in a separate lookup call from Dataweave reduce operator
  B. Call each API request in a separate route of a Scatter-Gather
  C. Call each API request in a separate route of a Parallel For Each scope
  D. Call each API request in a separate Async scope
  B. Call each API request in a separate route of a Scatter-Gather

  ---

  Scatter-Gather sends a request message to multiple targets concurrently. It collects the responses from all routes, and aggregates them into a single message.

  https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

• Question 69:

  What requirement prevents using Anypoint MQ as the messaging broker for a Mule application?

  A. When the payload sent through the message broker must use XML format
  B. When the payload sent through the message broker must be encrypted
  C. When the messaging broker must support point-to-point messaging
  D. When the messaging broker must be deployed on-premises
  D. When the messaging broker must be deployed on-premises

  ---

  Anypoint MQ is a cloud-based messaging service provided by MuleSoft, and it cannot be deployed on-premises. If there is a requirement for the messaging broker to be deployed on-premises, Anypoint MQ would not be suitable. Other considerations such as payload format (XML), encryption, and point-to-point messaging are supported by Anypoint MQ, but the deployment environment requirement is a critical constraint.

  References MuleSoft Anypoint MQ Documentation Cloud vs. On-Premises Messaging Solutions

• Question 70:

  A Mule application currently writes to two separate SQL Server database instances across the internet using a single XA transaction. It is 58. proposed to split this one transaction into two separate non-XA transactions with no other changes to the Mule application. What non-functional requirement can be expected to be negatively affected when implementing this change?

  A. Throughput
  B. Consistency
  C. Response time
  D. Availability
  B. Consistency

  ---

  Correct answer is Consistency as XA transactions are implemented to achieve this. XA transactions are added in the implementation to achieve goal of ACID properties. In the context of transaction processing, the acronym ACID refers to the four key properties of a transaction: atomicity, consistency, isolation, and durability. Atomicity : All changes to data are performed as if they are a single operation. That is, all the changes are performed, or none of them are. For example, in an application that transfers funds from one account to another, the atomicity property ensures that, if a debit is made successfully from one account, the corresponding credit is made to the other account. Consistency : Data is in a consistent state when a transaction starts and when it ends.For example, in an application that transfers funds from one account to another, the consistency property ensures that the total value of funds in both the accounts is the same at the start and end of each transaction. Isolation : The intermediate state of a transaction is invisible to other transactions. As a result, transactions that run concurrently appear to be serialized. For example, in an application that transfers funds from one account to another, the isolation property ensures that another transaction sees the transferred funds in one account or the other, but not in both, nor in neither. Durability : After a transaction successfully completes, changes to data persist and are not undone, even in the event of a system failure. For example, in an application that transfers funds from one account to another, the durability property ensures that the changes made to each account will not be reversed.

  MuleSoft reference: https://docs.mulesoft.com/mule-runtime/4.3/xa-transactions