2026 Updated Verified Salesforce-MuleSoft-Developer-II dumps Q&As - 100% Pass Guaranteed
Provide Valid Dumps To Help You Prepare For Salesforce Certified MuleSoft Developer II Exam
NEW QUESTION # 15
A Flight Management System publishes gate change notification events whenever a flight's arrival gate changes. Other systems, including Baggage Handler System. Inflight Catering System and Passenger Notifications System, must each asynchronously receive the same gate change notification to process the event according.
Which configuration is required in Anypoint MQ to achieve this publish/subscribe model?
- A. Publish the gate change notification to an Anypoint MQ queue.
Create different anypoint MQ exchange meant for each of the other subscribing systems Bind the queue with each of the exchanges - B. Publish each client subscribe directly to the exchange.
Have each client subscribe directly to the queue. - C. Publish the gate change notification to an Anypoint MC queue
Have each client subscribe directly to the queue - D. Publish the gate change notification to an Anypoint MQ exchanhe.
Create different Anypoint MQ queues meant for each of the other subscribing systems.Bind the exchange with each of the queues.
Answer: D
Explanation:
To achieve a publish/subscribe model using Anypoint MQ, where each system receives the same gate change notification event, the developer should publish the gate change notification to an Anypoint MQ exchange, create different Anypoint MQ queues meant for each of the other subscribing systems, and bind the exchange with each of the queues. An exchange is a message routing agent that can send messages to different queues based on predefined criteria. By binding an exchange with multiple queues, each queue receives a copy of every message sent to that exchange. Therefore, each system can subscribe to its own queue and receive every gate change notification event. Reference: https://docs.mulesoft.com/anypoint-mq/3.x/anypoint-mq-exchanges
NEW QUESTION # 16
Refer to the exhibit.
A Mule application pom.xml configures the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/certs directory.
Which configuration of this plugin achieves a successful build?
- A.
- B.
- C.
- D.
Answer: A
Explanation:
To configure the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/certs directory, option C should be used. This option specifies that any files with .cer or .jks extensions under the certs directory should be excluded from filtering. Filtering is a process of replacing placeholders with actual values in resource files during the build process. Binary files should not be filtered because they may become corrupted or unusable. Reference: https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html https://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html
NEW QUESTION # 17
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. Enable the CorrelationID checkbox in the HTTP Listener configuration
- C. NO action is needed as the correlation ID is returned to the caller in the response header by default
- D. Configure a custom correlation policy
Answer: C
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 # 18
A healthcare portal needs to validate the token that it sends to a Mule API. The developer plans to implement a custom policy using the HTTP Policy Transform Extension to match the token received in the header from the heathcare portal.
Which files does the developer need to create in order to package the custom policy?
- A. JSON properties file, XML template file
- B. JSON properties file, YAML configuration file
- C. XML template file, YAML configuration file
- D. Deployable ZIP file, YAML configuration file
Answer: C
Explanation:
To package a custom policy using the HTTP Policy Transform Extension, the developer needs to create an XML template file and a YAML configuration file. The XML template file defines the policy logic using Mule components and placeholders for user-defined properties. The YAML configuration file defines the metadata of the policy, such as its name, description, category, parameters, and dependencies. Reference: https://docs.mulesoft.com/api-manager/2.x/http-policy-transform#packaging-the-policy
NEW QUESTION # 19
A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.
- A. Any of the APIkit generate implement flows
- B. The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
- C. Northing because flowRef is an optional attribute which can be passed runtime
- 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 # 20
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:400
- B. HTTP status code:200
- C. HTTP status code:403
- D. HTTP status code:500
Answer: C
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 # 21
A developer has created the first version of an API designed for business partners to work commodity prices.
What should developer do to allow more than one major version of the same API to be exposed by the implementation?
- A. In Design Center, open the RAML and modify each operation to include the major version number
- B. In Anypoint Studio, generate scaffolding from the RAML, and the modify the <http:listerner> in the generated flows to include a parameter to replace the version number
- C. In Anypoint Studio, generate scaffolding from the RAML, and then modify the flow names generated by APIKit to include a variable with the major version number
- D. In Design Center, open the RAML and modify baseUn to include a variable that indicates the version number
Answer: D
Explanation:
To allow more than one major version of the same API to be exposed by the implementation, the developer should modify the baseUri property in the RAML file to include a variable that indicates the version number. The baseUri property defines the base URL of the API and can include variables that are replaced with actual values when mocking or deploying the API. By using a variable for the version number, the developer can expose different versions of the API using different base URLs and avoid conflicts or confusion. Reference: https://docs.mulesoft.com/api-designer/design-modify-raml-specs#baseuri https://docs.mulesoft.com/api-manager/2.x/api-versioning
NEW QUESTION # 22
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 and have the Exchange Administrator permission
- 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 configure the SLA tier for the application
- D. To only have Exchange Administrator permission
Answer: D
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 # 23
A company with MuleSoft Titanium develops a Salesforce System API using MuleSoft out-of-the-box Salesforce Connector and deploys the API to CloudHub.
Which steps provide the average number of requests and average response time of the Salesforce Connector?
- A. Access Anypoint Monitoring's built-in dashboard. Select a resource.
Locate the information under the Connectors tab. - B. Access Anypoint Monitoring's built-in dashboard
Seclect a resource.
Create a custom dashboard to retrieve the information. - C. Access Anypoint Monitoring built-in dashboard.
Select a resource.
Locate the information under Log Manager < Raw Data. - D. Change the API Implementation to capture the information in the log.
Retrieve the information from the log file.
Answer: A
Explanation:
To get the average number of requests and average response time of the Salesforce Connector, the developer should access Anypoint Monitoring's built-in dashboard, select a resource (such as an application or an API), and locate the information under the Connectors tab. The Connectors tab shows metrics for each connector used by the resource, such as average requests per minute, average response time, and failures. Reference: https://docs.mulesoft.com/monitoring/built-in-dashboard-reference
NEW QUESTION # 24
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. Settings.xml
- B. Pom.xml
- C. Config.yaml
- D. Mule.artificact.json
Answer: B
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 # 25
Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?
- A. A database as a transactional outbox and an Until Successful router to retry any requests
- B. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
- C. A Parallel for Each scope with each HTTP request wrapped in a Try scope
- D. VM queues as a reliability pattern with error handlers to roll back any requests
Answer: B
Explanation:
To invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures by executing compensating actions. Therefore, using a Scatter-Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/saga
NEW QUESTION # 26
Multiple individual Mute application need to use the Mule Maven plugin to deploy to CloudHub.
The plugin configuration should .. reused where necessary and anything project, specific should be property-based.
Where should the Mule Maven details be configured?
- A. Pom, xml
- B. A parent pom.xml
- C. A Bill of Materials (BOM) parent pm
- D. Settings, xml
Answer: B
Explanation:
To reuse Mule Maven plugin configuration across multiple individual Mule applications, the developer should use a parent pom.xml file. A parent pom.xml file defines common configuration for one or more child projects that inherit from it. The developer can specify common properties and dependencies for all child projects in the parent pom.xml file, such as Mule Maven plugin configuration, and then reference them in each child project's pom.xml file using placeholders. Reference: https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#parent-pom https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance
NEW QUESTION # 27
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?
- A. OS:KEY_NOT_FOUND
- B. nullPayload
- C. originalPayload
- D. testPayload
Answer: B
Explanation:
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
NEW QUESTION # 28
Which statement is true when working with correlation IDS?
- A. The HTTP Listener regenerates correlation IDs regardless of the HTTP request
- B. The Anypoint MQ Connector automatically propagates correlation IDS
- C. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
- D. The VM Connector does not automatically propagate correction IDs
Answer: C
Explanation:
When working with correlation IDs, the HTTP Listener generates correlation IDs unless a correlation ID is received in the HTTP request. In that case, it propagates the received correlation ID throughout the flow execution. Correlation IDs are used to track events across different flows or applications. Reference: https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#message-attributes
NEW QUESTION # 29
A mule application exposes and API for creating payments. An Operations team wants to ensure that the Payment API is up and running at all times in production.
Which approach should be used to test that the payment API is working in production?
- A. Configure the application to send health data to an external system
- B. Create a health check endpoint that reuses the same port number and HTTP Listener configuration as the API itself
- C. Monitor the Payment API directly sending real customer payment data
- D. Create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API
Answer: D
Explanation:
To test that the payment API is working in production, the developer should create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API. This way, the developer can isolate the health check endpoint from the API traffic and avoid affecting the performance or availability of the API. The health check endpoint should return a simple response that indicates the status of the API, such as OK or ERROR. Reference: https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor#create-a-monitor
NEW QUESTION # 30
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. In Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.
- B. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
- C. 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. - D. 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.
Answer: D
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 # 31
Refer to the exhibit.
What action must be performed to log all the errors raised by the VM Connector?
- A. Configure <Logger level-'ERROR'/> inside the VM Connector configuration
- B. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'/> inside the Appenders tag
- C. Nothing, as error-level events are automatically logged
- D. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'I> inside the Logger tag
Answer: B
Explanation:
To log all the errors raised by the VM Connector, the developer needs to add an async logger with the name 'org.mule.extension.vm' and the level 'ERROR' inside the appenders tag of the log4j2.xml file. This will enable logging all error-level events generated by the VM Connector to the console appender. Reference: https://docs.mulesoft.com/mule-runtime/4.3/logging-in-mule#configuring-custom-logging-settings
NEW QUESTION # 32
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. External callback URL, access token URL, client ID, response refresh token
- D. Token URL, authorization URL, client ID, client secret local callback URL
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 # 33
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 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases
- B. Chain together the test suites and test cases for Flow-1 and Flow-2
- C. Use ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent
- D. Use ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases
Answer: C
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 # 34
Refer to the exhibit.
What required changes can be made to give a partial successful response in case the United Airlines API returns with a timeout?
- A. Add Flow Reference components inside a Try scope.
Set the payload to a default value'' insider the error handler using the ON Error Continue scope - B. Add Flow Reference components inside a Try scope
Set the payload to a default value '' inside the error handler using the On Error Propagate scope - C. Add a Scatter-gather component inside a Try scope.
Set the payload to a default value 'Error' inside the error handler using the On Error Propagate scope. - D. Add a Scatter-Gather component inside a Try scope.
Set the payload to a default value 'Error'' inside the error handler using the On Error Continue scope.
Answer: D
Explanation:
To give a partial successful response in case the United Airlines API returns with a timeout, the developer should add a Scatter-Gather component inside a Try scope, and set the payload to a default value 'Error' inside the error handler using the On Error Continue scope. A Scatter-Gather component allows sending multiple requests concurrently and aggregating the responses into an array. A Try scope allows handling errors that occur within it using an error handler. An On Error Continue scope allows continuing the flow execution after handling an error. Therefore, by using these components, the developer can send requests to both APIs in parallel, handle any timeout errors from United Airlines API, and return a partial response with a default value for that API. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/try-scope-concept https://docs.mulesoft.com/mule-runtime/4.3/on-error-continue-concept
NEW QUESTION # 35
......
Achieve Success in Actual Salesforce-MuleSoft-Developer-II Exam Salesforce-MuleSoft-Developer-II Exam Dumps: https://www.actualtestsit.com/Salesforce/Salesforce-MuleSoft-Developer-II-exam-prep-dumps.html