Salesforce MuleSoft Developer II Exam Practice Test Instant Access

Question 1

Two APIs are deployed to a two-node on-prem cluster. Due to a requirements change, the two APIs must communicate to exchange data asynchronously.

AIf the two APIs use the same domain, the VM Connector can be leveraged

BThe VM Connector is used to inter-application communication, so it is not possible to use the VM Connector

CInstead of using the VM Connector use <flow-ref>directly

DIt is not possible to use the VM Connector since the APIs are running in a cluster mode and each mode has it own set of VM Queues

Answer : A

To communicate asynchronously between two APIs deployed to a two-node on-prem cluster, the developer can use the VM Connector if the two APIs use the same domain. The VM Connector allows passing messages between different Mule applications within a single Mule runtime instance or across different instances using shared memory or persistent storage. If two APIs are deployed under the same domain, they can share resources such as VM queues and communicate asynchronously using VM Connector operations. Reference: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector https://docs.mulesoft.com/mule-runtime/4.3/shared-resources

Question 2

Refer to the exhibit.

A Mute Object Store is configured with an entry TTL of one second and an expiration interval of 30 seconds.

What is the result of the flow if processing between os'store and os:retrieve takes 10 seconds?

AnullPayload

BoriginalPayload

COS:KEY_NOT_FOUND

DtestPayload

Answer : A

The result of the flow is nullPayload if processing between os:store and os:retrieve takes 10 seconds. This is because the entry TTL of the object store is one second, which means that any stored value expires after one second and is removed from the object store. The expiration interval of 30 seconds only determines how often the object store checks for expired values, but it does not affect the TTL. Therefore, when os:retrieve tries to get the value after 10 seconds, it returns nullPayload because the value has already expired and been removed. Reference: https://docs.mulesoft.com/object-store/osv2-faq#how-does-the-time-to-live-work

Question 3

A Mule application need to invoice an API hosted by an external system to initiate a process. The external API takes anywhere between one minute and 24 hours to compute its process.

Which implementation should be used to get response data from the external API after it completes processing?

AUse an HTTP Connector to invoke the API and wait for a response

BUse a Scheduler to check for a response every minute

CUse an HTTP Connector inside Async scope to invoice the API and wait for a response

DExpose an HTTP callback API in Mule and register it with the external system

Answer : D

To get response data from the external API after it completes processing, the developer should expose an HTTP callback API in Mule and register it with the external system. This way, the external API can invoke the callback API with the response data when it is ready, instead of making the Mule application wait for a long time or poll for a response repeatedly. Reference: https://docs.mulesoft.com/mule-runtime/4.3/http-listener-ref#callback

Question 4

In a Mule project, Flow-1 contains a flow-ref to Flow-2 depends on data from Flow-1 to execute successfully.

Which action ensures the test suites and test cases written for Flow-1 and Flow-2 will execute successfully?

AChain together the test suites and test cases for Flow-1 and Flow-2

BUse ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent

CUse ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases

DUse 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases

Answer : B

To ensure the test suites and test cases written for Flow-1 and Flow-2 will execute successfully, the developer should use a Set Event processor to pass the input that is needed by Flow-2, and keep the test cases for Flow-1 and Flow-2 independent. This way, the developer can isolate the testing of each flow and avoid coupling them together. Reference: https://docs.mulesoft.com/munit/2.3/munit-test-flow

Question 5

A Mule application defines as SSL/TLS keystore properly 'tis,keystore.keyPassword'' as secure.

How can this property be referenced to access its value within the application?

A#{secure::tiskeystore,keyPassowrd}

B${secure::tiskeystore,keyPassowrd}

C${secure::tiskeystore,keyPassowrd}

Dp{secure::tiskeystore,keyPassowrd}

Answer : B

secure::tiskeystore,keyPassowrdShortExplanationofCorrectAnswerOnly:Toreferenceasecurepropertyvaluewithintheapplication,thedeveloperneedstousethesyntax{secure::}. In this case, the property name is tiskeystore,keyPassword, so the correct syntax is ${secure::tiskeystore,keyPassowrd}. Reference: https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration-properties#referencing-secure-properties

Question 6

Which statement is true when using XML SDK for creating custom message processors?

AProperties are fields defined by an end user of the XML SDK component and serve as a global configuration for the entire Mule project in which they are used

BAn XML SDK provides both inbound and outbound operations

COperations can be reused in recursive calls

DAll operations are public

Answer : A

When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or protected in XML SDK. Reference: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#operations

Question 7

Which statement is true about using mutual TLS to secure an application?

AMutual TLS requires a hardware security module to be used

BMutual TLS authenticates the identity of the server before the identity of the client

CMutual TLS ensures only authorized end users are allowed to access an endpoint

DMutual TLS increases the encryption strength versus server-side TLS alone

Answer : B

Mutual TLS (mTLS) is an extension of TLS that requires both parties (client and server) to present their certificates to each other during the handshake process. This way, both parties can verify each other's identity and establish a secure connection. The authentication of the server happens before the authentication of the client, as the server sends its certificate first and then requests the client's certificate. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-authentication

Salesforce MuleSoft Developer II Salesforce Certified MuleSoft Developer II Exam Practice Test