Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Exam Questions Instant Access

Question 1

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

ASupport for TLS mutual (two-way) authentication with HTTP clients

BEncryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and https://customer.com/api)

CEncryption of both HTTP request and HTTP response bodies for all HTTP clients

DEncryption of both HTTP request header and HTTP request body for all HTTP clients

Answer : A

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 isSupport for TLS mutual (two-way) authentication with HTTP clients.

Question 2

A new Mule application under development must implement extensive data transformation logic. Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.

The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.

What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?

AImplement and expose all transformation logic as mlaoservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application

BImplement transformation logic in the new Mute application using DataWeave, replicating the transformation logic of existing transformation services

CExtend the existing transformation services with new transformation logic and Invoke them from the new Mule application

DImplement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible

Answer : D

Correct answer is Implement transformation logic in the new Mule application using DataWeave, invoking existing transformation services when possible. * The key here minimal testing effort, 'Extend existing transformation logic' is not a feasible option because additional functionality is highly specific to the new Mule application so it should not be a part of commonly used functionality. So this option is ruled out. * 'Implement transformation logic in the new Mule application using DataWeave, replicating the transformation logic of existing transformation services' Replicating the transformation logic of existing transformation services will cause duplicity of code. So this option is ruled out. * 'Implement and expose all transformation logic as microservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application' as question specifies that the transformation is app specific and wont be used outside

Question 3

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?

ACheck the Persistent VM queues checkbox in the application deployment configuration

BCheck the Non-persistent VM queues checkbox in the application deployment configuration

CIn the Runtime Manager Properties tab, disable persistent VM queues for Batch Job scopes

DIn the Runtime Manager Properties tab, enable persistent VM queues for the FTPS connector

Answer : A

Question 4

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?

AEach 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

BEach 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

CEach 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

DEach 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

Answer : A

*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.

*RECORDSare 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 batchjob instance id.

Question 5

What is true about the network connections when a Mule application uses a JMS connector to interact with a JMS provider (message broker)?

ATo complete sending a JMS message, the JMS connector must establish a network connection with the JMS message recipient

BTo receive messages into the Mule application, the JMS provider initiates a network connection to the JMS connector and pushes messages along this connection

CThe JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider

DThe AMQP protocol can be used by the JMS connector to portably establish connections to various types of JMS providers

Answer : C

* To send message or receive JMS (Java Message Service) message no separate network connection need to be established. So option A, C and D are ruled out.

Correct Answer: The JMS connector supports both sending and receiving of JMS

* JMS Connector enables sending and receiving messages to queues and topics for any message service that implements the JMS specification.

* JMS is a widely used API for message-oriented middleware.

* It enables the communication between different components of a distributed application to be loosely coupled, reliable, and asynchronous.

MuleSoft Doc Reference:https://docs.mulesoft.com/jms-connector/1.7/

Question 6

An airline is architecting an API connectivity project to integrate its flight data into an online aggregation website. The interface must allow for secure communication high-performance and asynchronous message exchange.

What are suitable interface technologies for this integration assuming that Mulesoft fully supports these technologies and that Anypoint connectors exist for these interfaces?

AAsyncAPI over HTTPS
AMQP with RabbitMQ JSON/REST over HTTPS

BXML over ActiveMQ XML over SFTP XML/REST over HTTPS

CCSV over FTP YAM L over TLS JSON over HTTPS

DSOAP over HTTPS HOP over TLS gRPC over HTTPS

Answer : A

Question 7

An organization is evaluating using the CloudHub shared Load Balancer (SLB) vs creating a CloudHub dedicated load balancer (DLB). They are evaluating how this choice affects the various types of certificates used by CloudHub deplpoyed Mule applications, including MuleSoft-provided, customer-provided, or Mule application-provided certificates.

What type of restrictions exist on the types of certificates that can be exposed by the CloudHub Shared Load Balancer (SLB) to external web clients over the public internet?

AOnly MuleSoft-provided certificates are exposed.

BOnly customer-provided wildcard certificates are exposed.

COnly customer-provided self-signed certificates are exposed.

DOnly underlying Mule application certificates are exposed (pass-through)

Answer : A

https://docs.mulesoft.com/runtime-manager/dedicated-load-balancer-tutorial