Updated Feb-2025 Salesforce-MuleSoft-Developer-II Exam Practice Test Questions
Verified Salesforce-MuleSoft-Developer-II dumps Q&As 100% Pass in First Attempt Guaranteed Updated Dump
Salesforce Salesforce-MuleSoft-Developer-II Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 36
Which statement is true when using XML SDK for creating custom message processors?
- A. Properties 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
- B. Operations can be reused in recursive calls
- C. An XML SDK provides both inbound and outbound operations
- D. All operations are public
Answer: A
Explanation:
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
NEW QUESTION # 37
Which statement is true when working with correlation IDS?
- A. The HTTP Listener regenerates correlation IDs regardless of the HTTP request
- B. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
- C. The VM Connector does not automatically propagate correction IDs
- D. The Anypoint MQ Connector automatically propagates correlation IDS
Answer: B
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 # 38
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. Deployable ZIP file, YAML configuration file
- B. JSON properties file, YAML configuration file
- C. XML template file, YAML configuration file
- D. JSON properties file, XML template 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 # 39
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. Configure a custom correlation policy
- B. NO action is needed as the correlation ID is returned to the caller in the response header by default
- C. Enable the auto-generate CorrelationID option when scaffolding the flow
- 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 # 40
A Mule API receives a JSON payload and updates the target system with the payload. The developer uses JSON schemas to ensure the data is valid.
How can the data be validation before posting to the target system?
- A. Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema
- B. Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
- C. Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add:
%dw 2.0
Import.json-moduls - D. Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
Answer: A
Explanation:
To validate the data before posting to the target system, the developer should add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema. The JSON module provides a validate-schema operation that validates a JSON payload against a JSON schema and throws an error if the payload is invalid. Reference: https://docs.mulesoft.com/json-module/1.1/json-validate-schema
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. Create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager
- B. Pass in the runtime parameter ''-Danpow.platform.gatekeeper=disabled''
- C. Run the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager
- D. Deactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio
Answer: B
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
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. Mule.artificact.json
- B. Pom.xml
- C. Config.yaml
- D. Settings.xml
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 # 43
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 # 44
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. originalPayload
- B. nullPayload
- C. testPayload
- D. OS:KEY_NOT_FOUND
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 # 45
Which type of cache invalidation does the Cache scope support without having to write any additional code?
- A. Notification-based invalidation
- B. Time to live
- C. Write-through invalidation
- D. White-behind invalidation
Answer: B
Explanation:
The Cache scope supports time to live (TTL) as a cache invalidation strategy without having to write any additional code. TTL specifies how long the cached response is valid before it expires and needs to be refreshed. The Cache scope also supports custom invalidation strategies using MEL or DataWeave expressions. Reference: https://docs.mulesoft.com/mule-runtime/4.3/cache-scope#cache_invalidation
NEW QUESTION # 46
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. In Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.
- C. 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. - D. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
Answer: C
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 # 47
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: C
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 # 48
A company has been using CI/CD. Its developers use Maven to handle build and deployment activities.
What is the correct sequence of activities that takes place during the Maven build and deployment?
- A. Validate, initialize, compile, test package, verify, install, deploy
- B. Initialize, validate, compute, test, package, verify, install, deploy
- C. Validate, initialize, compile, package, test, install, verify, verify, deploy
- D. Validation, initialize, compile, test, package, install verify, deploy
Answer: A
Explanation:
The correct sequence of activities that takes place during the Maven build and deployment is validate, initialize, compile, test package, verify, install, deploy. These are Maven lifecycle phases that define a sequence of goals to execute during a build process. Each phase represents a stage in the build lifecycle and can have zero or more goals bound to it. Reference: https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
NEW QUESTION # 49
The HTTP Request operation raises an HTTP CONNECTIVITY error.
Which HTTP status code and body are returned to the web client?
- A. HTTP Status Code:500.
Body 'The HTTP CONNECTIVITY Error description - B. HTTP Status Code:500.
Body 'Error in processing your request - C. HTTP Status Code:500.
Body 'Error in processing your request - D. HTTP Status Code:200.
Body 'Error in processing your request
Answer: B
Explanation:
When the HTTP Request operation raises an HTTP CONNECTIVITY error, it triggers an on-error-continue handler that sets a payload with 'Error in processing your request'. Since no status code is explicitly set in this handler, it defaults to 500 (INTERNAL SERVER ERROR). Therefore, the web client receives an HTTP response with status code 500 and body 'Error in processing your request'. Reference: https://docs.mulesoft.com/mule-runtime/4.3/error-handling#on-error-continue
NEW QUESTION # 50
An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication using Anypoint MQ. Each message must be correlated against the original order ID for observability and tracing.
How should a developer propagate the order ID as the correlation ID across each message?
- A. Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
- B. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
- C. Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
- D. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
Answer: A
Explanation:
To propagate the order ID as the correlation ID across each message using Anypoint MQ, the developer should wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID. The With CorrelationID scope allows setting a custom correlation ID for any event that occurs within it. The Tracing module also enables distributed tracing across different Mule applications and services using Anypoint Monitoring. Reference: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#with-correlation-id-scope https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts
NEW QUESTION # 51
Which configurations are required for HTTP Listener to enable mTLS authentication?
- A. Set an appropriate keystore configuration and use persistent connections for the listener
- B. Set an appropriate reconnection strategy and use persistent connections for the listener
- C. Set an appropriate keystore and truststore configuration for the listener
- D. Set an appropriate truststore configuration and reconnection strategy for the listener
Answer: C
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 # 52
A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.
- A. The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
- B. Any of the APIkit generate implement flows
- C. The name of the flow that has APlkit Console to receive all incoming RESTful operation requests.
- D. Northing because flowRef is an optional attribute which can be passed runtime
Answer: A
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 # 53
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 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. - B. 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. - C. 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 - D. 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
Answer: A
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 # 54
......
Pass Salesforce MuleSoft Salesforce-MuleSoft-Developer-II Exam With 62 Questions: https://www.actual4labs.com/Salesforce/Salesforce-MuleSoft-Developer-II-actual-exam-dumps.html