100% Free Salesforce MuleSoft Salesforce-MuleSoft-Developer-II Dumps PDF Demo Cert Guide Cover
PDF Exam Material 2025 Realistic Salesforce-MuleSoft-Developer-II Dumps Questions
Salesforce Salesforce-MuleSoft-Developer-II Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 23
A Mule application deployed to a standardalone Mule runtime uses VM queues to publish messages to be consumed asynchronously by another flow.
In the case of a system failure, what will happen to in-flight messages in the VM queues that have been consumed?
- A. For persistent queues, the message will be processed after the system comes online
- B. For any type of queue, the message will be lost
- C. For transient queues, the message will be processed after the system comes online
- D. For nay type of queue, the message will be processed after the system comes online
Answer: A
Explanation:
In case of a system failure, in-flight messages in persistent VM queues that have been consumed will be processed after the system comes online. This is because persistent VM queues store messages on disk and guarantee delivery even if there is a system crash or restart. Therefore, any in-flight messages that have been consumed but not processed will be recovered from disk and processed when the system is back online. Reference: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector#persistent-queues
NEW QUESTION # 24
A Mule application for processing orders must log the order ID for every log message output.
What is a best practice to enrich every log message with the order ID?
- A. Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
- B. Use flow variables within every logger processor to log the order ID
- C. Use the Tracing module to set logging variables with a Mapped Diagnostic Context
- D. Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern
Answer: C
Explanation:
To enrich every log message with the order ID, the developer should use the Tracing module to set logging variables with a Mapped Diagnostic Context (MDC). The Tracing module allows adding custom key-value pairs to log messages using MDC variables. The developer can use Set Logging Variables operation to set the order ID as an MDC variable and then use it in any logger processor within the same thread or event. Reference: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#set-logging-variables
NEW QUESTION # 25
Which plugin or dependency is required to unit test modules created with XML SDK?
- A. Junit
- B. MUnit Extensions Maven plugin
- C. MUnit Maven plugin
- D. XMLUnit
Answer: B
Explanation:
To unit test modules created with XML SDK, the developer needs to use the MUnit Extensions Maven plugin. This plugin allows testing XML SDK modules using MUnit by adding a dependency to the module under test and using a custom processor tag to invoke it. Reference: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#testing
NEW QUESTION # 26
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?
- A. Use ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent
- B. Use 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases
- C. Use ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases
- D. Chain together the test suites and test cases for Flow-1 and Flow-2
Answer: A
Explanation:
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
NEW QUESTION # 27
What is the MuleSoft recommended method to encrypt sensitive property data?
- A. The encryption key should be identical for all environments and the sensitive data should be different for each environment
- B. The encryption key and sensitive data should be different for each environment
- C. The encryption key should be identical for all environments
- D. The encryption key should be different for each environment and the sensitive data should be the same for all environments
Answer: B
Explanation:
The MuleSoft recommended method to encrypt sensitive property data is to use the Secure Properties Tool that comes with Anypoint Studio. This tool allows encrypting properties files with a secret key and then decrypting them at runtime using the same key. The encryption key and sensitive data should be different for each environment to ensure security and avoid accidental exposure of sensitive data. Reference: https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration-properties
NEW QUESTION # 28
A scatter-gather router is configured with four routes:Route A, B, C and D.
Route C false.
- A. Error,errorMessage,payload.failures['2']
- B. Payload ['2']
- C. Payload failures['2']
- D. Error,errorMesage.payload.results ['2']
Answer: D
Explanation:
The result of accessing route C failure is Error,errorMessage,payload.failures['2']. This is because a scatter-gather router returns an aggregated message that contains an array of results from each route and an array of failures from each route. The failures array contains error objects with information about each failed route execution. To access route C failure, which is the third route (index 2), the developer needs to use Error.errorMessage.payload.failures['2'] expression. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-reference#scatter-gather-output
NEW QUESTION # 29
When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?
- A. The Public key format
- B. The TLS version
- C. A protocol
- D. An encryption algorithm
Answer: D
Explanation:
A cipher suite is a set of cryptographic algorithms that are used to secure the communication between a client and a server. A cipher suite consists of four components: a key exchange algorithm, an authentication algorithm, an encryption algorithm, and a message authentication code (MAC) algorithm. During the cipher suite exchange, the client and the server agree on which encryption algorithm to use for encrypting and decrypting the data. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#cipher-suites
NEW QUESTION # 30
A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.
- A. Northing because flowRef is an optional attribute which can be passed runtime
- B. The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
- C. Any of the APIkit generate implement flows
- D. The name of the flow that has APlkit Console to receive all incoming RESTful operation requests.
Answer: B
Explanation:
To use API autodiscovery to access and enforce policies for a RESTful implementation, flowRef must be set to the name of the flow that has HTTP listener to receive all incoming RESTful operation requests. This way, API autodiscovery can identify the API implementation and associate it with the corresponding API specification and policies in API Manager. The flow that has HTTP listener is usually the main flow that contains the APIKit Router. Reference: https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#flowref
NEW QUESTION # 31
The Center for Enablement team published a common application as a reusable module to the central Nexus repository.
How can the common application be included in all API implementations?
- A. Add a Maven dependency in the PCM file with multiple-plugin as <classifier>
- B. Add a Maven dependency in the POM file with jar as <classifier>
- C. Download the common application from Naxus and copy it to the src/main/resources folder in the API
- D. Copy the common application's source XML file and out it in a new flow file in the src/main/mule folder
Answer: B
Explanation:
To include a common application as a reusable module in all API implementations, the developer should add a Maven dependency in the POM file with jar as <classifier>. This way, the developer can reuse Mule code from another application by packaging it as a JAR file and adding it as a dependency in the POM file of the API implementation. The classifier element specifies that it is a JAR file. Reference: https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#add-a-maven-dependency-to-the-pom-file
NEW QUESTION # 32
A new Mule project has been created in Anypoint Studio with the default settings.
Which file inside the Mule project must be modified before using Maven to successfully deploy the application?
- A. Pom.xml
- B. Config.yaml
- C. Mule.artificact.json
- D. Settings.xml
Answer: A
Explanation:
To use Maven to successfully deploy the application, the developer needs to modify the pom.xml file inside the Mule project. The pom.xml file contains the configuration and dependencies of the Mule application, as well as the deployment information such as the CloudHub region, environment, and worker size. The developer needs to specify these properties in the pom.xml file before using Maven to deploy the application. Reference: https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#application-deployment-descriptor
NEW QUESTION # 33
When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID back to the caller in the HTTP response header.
How can this be achieved?
- A. Enable the auto-generate CorrelationID option when scaffolding the flow
- B. NO action is needed as the correlation ID is returned to the caller in the response header by default
- C. Configure a custom correlation policy
- D. Enable the CorrelationID checkbox in the HTTP Listener configuration
Answer: B
Explanation:
When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID, which is returned to the caller in the response header by default as MULE_CORRELATION_ID. Reference: https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#message-attributes
NEW QUESTION # 34
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. p{secure::tiskeystore,keyPassowrd}
- D. ${secure::tiskeystore,keyPassowrd}
Answer: A
Explanation:
secure::tiskeystore,keyPassowrd∗∗ShortExplanationofCorrectAnswerOnly: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
NEW QUESTION # 35
When registering a client application with an existing API instance or API Group instance, what is required to manually approve or reject request access?
- A. To configure the SLA tier for the application
- B. To configure the SLA tier for the application and have the role of Organization Administrator, API Manager Environment Administrator, or the Manage Contacts permission
- C. To only have Exchange Administrator permission
- D. To configure the SLA tier for the application and have the Exchange Administrator permission
Answer: C
Explanation:
To manually approve or reject request access when registering a client application with an existing API instance or API Group instance, it is required to configure the SLA tier for the application and have one of the following roles or permissions: Organization Administrator, API Manager Environment Administrator, or Manage Contracts permission. These roles or permissions allow managing client applications and contracts in API Manager. Reference: https://docs.mulesoft.com/api-manager/2.x/client-applications#managing-client-applications-and-contracts
NEW QUESTION # 36
The flow is invoicing a target API. The API's protocol is HTTPS. The TLS configuration in the HTTP Request Configuration global element is set to None. A web client submits a request to http:localhost:8081/vehicles.
If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP Request operation when the flow executes?
- A. The HTTP Request operation will always fail regardless of the CA
- B. The HTTP Request operation will always succeed regardless of the CA
- C. The HTTP Request operation will succeed if the CA's certificate is present in the JRE's default truststore.
- D. The HTTP Request operation will succeed if the CA'S certificate is present in the JRE's default keystore
Answer: C
Explanation:
The HTTP Request operation will use the default truststore of the JRE to validate the certificate of the target API. If the CA's certificate is present in the truststore, the operation will succeed. Otherwise, it will fail with a handshake exception. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#tls-default
NEW QUESTION # 37
An organization uses CloudHub to deploy all of its applications.
How can a common-global-handler flow be configured so that it can be reused across all of the organization's deployed applications?
- A. Create a Mule plugin project
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mute applications.
Import that configuration file in Mute applications. - B. Create a Mule Plugin project
- C. Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
Answer: B
Explanation:
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mule applications
D.
Create a Mule daman project.
Create a common-global-error-handler flow inside the domain project.
Use this domain project as a dependency.
Explanation:
To configure a common-global-handler flow that can be reused across all of the organization's deployed applications, the developer should create a Mule Plugin project, create a common-global-error-handler flow inside the plugin project, and use this plugin as a dependency in all Mule applications. This way, the developer can import the common-global-error-handler flow in any application that needs it and avoid duplicating the error handling logic. Reference: https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler
NEW QUESTION # 38
A Mule application includes a subflow containing a Scatter.Gather scope. Within each log of the Scatter.Gatter. an HTTP connector calls a PUT endpoint to modify records in different upstream system. The subflow is called inside an Unit successful scope to retry if a transitory exception is raised.
A technical spike is being performed to increase reliability of the Mule application.
Which steps should be performed within the Mule flow above the ensure idempontent behavior?
- A. Remove the Put requests from the Scatter-Getter and perform them sequentially
- B. Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails
- C. None, the flow already exhibits idempotent behavior
- D. Change the PUT requests inside the Scatter-Gather to POST requests
Answer: B
Explanation:
To ensure idempotent behavior within a Mule flow that contains a subflow with a Scatter-Gather scope, the developer should ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails. Idempotency means that multiple identical requests have the same effect as a single request. Therefore, if one of the HTTP requests inside the Scatter-Gather fails, the error-handling flow should undo any changes made by other successful requests to ensure consistency and avoid partial updates. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/error-handling
NEW QUESTION # 39
A company deploys 10 public APIs to CloudHub. Each API has its individual health endpoint defined. The platform operation team wants to configure API Functional Monitoring to monitor the health of the APIs periodically while minimizing operational overhead and cost.
How should API Functional Monitoring be configured?
- A. From one public location with all 10 APIs in a single schedule
- B. From 10 public locations with each API in its own schedule
- C. From one private location with all 10 APIs in a single schedule
- D. From one public location with each API in its own schedule
Answer: A
Explanation:
To configure API Functional Monitoring to monitor the health of 10 public APIs periodically while minimizing operational overhead and cost, the developer should use one public location with all 10 APIs in a single schedule. A public location is a worker that runs in a CloudHub shared environment, which is cheaper and easier to maintain than a private location. A single schedule allows running all 10 APIs tests at the same time and frequency, which reduces complexity and resource consumption. Reference: https://docs.mulesoft.com/functional-monitoring/fm-create-monitor#create-a-monitor
NEW QUESTION # 40
Refer to the exhibit.
A developer generates the base scaffolding for an API in Anypoint Studio.
Which HTTP status code is returned while testing using the API Kit console if no values are entered in client-secret?
- A. HTTP status code:200
- B. HTTP status code:500
- C. HTTP status code:400
- D. HTTP status code:403
Answer: D
Explanation:
Based on the code snippet and schema.json file below, when testing using the API Kit console if no values are entered in client-secret, HTTP status code 403 (FORBIDDEN) is returned. This is because client-secret is defined as a required header parameter in schema.json file, which means that it must be present in every request. If no values are entered in client-secret, then it is equivalent to omitting this header parameter, which violates the schema and causes APIKit Router to return HTTP status code 403. Reference: https://docs.mulesoft.com/apikit/4.x/apikit-4-headers
NEW QUESTION # 41
An API has been developed and deployed to CloudHub Among the policies applied to this API is an allowlist of IP addresses. A developer wants to run a test in Anypoint Studio and does not want any policies applied because their workstation is not included in the allowlist.
What must the developer do in order to run this test locally without the policies applied?
- A. Run the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager
- B. Deactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio
- C. Create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager
- D. Pass in the runtime parameter ''-Danpow.platform.gatekeeper=disabled''
Answer: D
Explanation:
To run a test locally without the policies applied, the developer should create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager. This way, the developer can use different configuration properties for different environments and avoid triggering API autodiscovery when running tests locally. API autodiscovery is a mechanism that associates an API implementation with its corresponding API specification and policies in API Manager based on its API instance ID. By setting this ID to a value that does not exist in API Manager, the developer can prevent API autodiscovery from finding and applying any policies to the local test. Reference: https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#configuring-api-autodiscovery https://docs.mulesoft.com/mule-runtime/4.3/configuring-properties
NEW QUESTION # 42
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.
- A. The VM Connector is used to inter-application communication, so it is not possible to use the VM Connector
- B. It 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
- C. If the two APIs use the same domain, the VM Connector can be leveraged
- D. Instead of using the VM Connector use <flow-ref>directly
Answer: C
Explanation:
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
NEW QUESTION # 43
Refer to the exhibit.
Based on the code snippet, schema,json file, and payload below, what is the outcome of the given code snippet when a request is sent with the payload?
- A. The Mule flow will throw the exception 'JSON:SCHEMA_NOT_HONOURED
- B. The Mule flow will execute successfully with status code 204
- C. The Mule flow will execute successfully with status code 200m and a response will display the message '' Age in years which must equal to or greater than zero.''
- D. The Mule flow will execute successfully with status code 200, and the response will be the JSON sent in request
Answer: A
Explanation:
Based on the code snippet, schema.json file, and payload below, the outcome of the given code snippet when a request is sent with the payload is that the Mule flow will throw the exception 'JSON:SCHEMA_NOT_HONOURED'. This is because the payload does not conform to the schema.json file, which specifies that age must be a number greater than or equal to zero. The payload has age as a string with a negative value, which violates the schema. Therefore, the validate-schema operation throws an error with type 'JSON:SCHEMA_NOT_HONOURED'. Reference: https://docs.mulesoft.com/json-module/1.1/json-validate-schema
NEW QUESTION # 44
Which properties are mandatory on the HTTP Connector configuration in order to use the OAuth 2.0 Authorization Code grant type for authentication?
- A. External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret
- B. External callback URL, access token URL, client ID response access token
- C. Token URL, authorization URL, client ID, client secret local callback URL
- D. External callback URL, access token URL, client ID, response refresh token
Answer: A
Explanation:
To use the OAuth 2.0 Authorization Code grant type for authentication, the HTTP Connector configuration requires the following properties: token URL, authorization URL, client ID, client secret, and local callback URL. The token URL is the endpoint of the authorization server that provides access tokens. The authorization URL is the endpoint of the authorization server that initiates the user consent flow. The client ID and client secret are the credentials of the Mule application registered with the authorization server. The local callback URL is the endpoint of the Mule application that receives the authorization code from the authorization server. Reference: https://docs.mulesoft.com/http-connector/1.6/http-authentication#oauth-2-0
NEW QUESTION # 45
Refer to the exhibits.
Bioinfo System API is implemented and published to Anypoint Exchange. A developer wants to invoke this API using its REST Connector.
What should be added to the POM?
- A.
- B.
- C.
- D.
- E.
Answer: A
Explanation:
To invoke Bioinfo System API using its REST Connector, option E should be added to the pom.xml file. This option adds a dependency for Bioinfo System API REST Connector with its group ID, artifact ID, version, classifier, and type. The classifier specifies that it is a REST Connector (raml-client), and the type specifies that it is a Mule plugin (mule-plugin). Reference: https://docs.mulesoft.com/apikit/4.x/apikit-4-generate-from-rest-api-task#add-the-api-dependency-to-the-pom-file
NEW QUESTION # 46
Which configurations are required for HTTP Listener to enable mTLS authentication?
- A. Set an appropriate keystore and truststore configuration for the listener
- B. Set an appropriate keystore configuration and use persistent connections for the listener
- C. Set an appropriate truststore configuration and reconnection strategy for the listener
- D. Set an appropriate reconnection strategy and use persistent connections for the listener
Answer: A
Explanation:
To enable mTLS authentication for HTTP Listener, the developer needs to set an appropriate keystore and truststore configuration for the listener. The keystore contains the certificate and private key of the Mule application that are used to prove its identity to clients. The truststore contains the certificates of trusted clients that are allowed to access the Mule application. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-authentication
NEW QUESTION # 47
A Mule implementation uses a HTTP Request within an Unit Successful scope to connect to an API.
How should a permanent error response like HTTP:UNAUTHORIZED be handle inside Until Successful to reduce latency?
- A. Put the HTTP Request inside a try scope in Unit Successful.
In the error handler, use On Error Propagate to catch permanent errors like HTTP UNAUTHORIZED. - B. Put the HTTP Request inside a try scope in Unit Successful.
In the error handler, use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED. - C. In Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.
- D. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
Answer: B
Explanation:
To handle a permanent error response like HTTP:UNAUTHORIZED inside Until Successful, the developer should put the HTTP Request inside a try scope in Unit Successful, and use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED in the error handler. This way, the developer can avoid retrying requests that will always fail due to a permanent error, and reduce latency. On Error Continue allows the flow to continue processing after handling the error. Reference: https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope https://docs.mulesoft.com/mule-runtime/4.3/on-error-continue-concept
NEW QUESTION # 48
......
Updated Salesforce Salesforce-MuleSoft-Developer-II Dumps – PDF & Online Engine: https://dumpstorrent.exam4pdf.com/Salesforce-MuleSoft-Developer-II-dumps-torrent.html
