Salesforce-MuleSoft-Developer-II Dumps (2024) Prepare Your Exam With 62 Questions [Q26-Q51]

Share

Salesforce-MuleSoft-Developer-II Dumps (2024) Prepare Your Exam With 62 Questions

New Salesforce-MuleSoft-Developer-II Dumps - Real Salesforce Exam Questions

NEW QUESTION # 26
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 transient queues, the message will be processed after the system comes online
  • B. For persistent queues, the message will be processed after the system comes online
  • C. For any type of queue, the message will be lost
  • D. For nay type of queue, the message will be processed after the system comes online

Answer: B

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 # 27
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 refresh token
  • C. External callback URL, access token URL, client ID response access 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 # 28
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. 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.
  • C. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
  • 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 # 29
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 ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases
  • B. Chain together the test suites and test cases for Flow-1 and Flow-2
  • C. Use 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases
  • D. Use ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent

Answer: D

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 # 30
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. A protocol
  • C. An encryption algorithm
  • D. The TLS version

Answer: C

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 # 31
Refer to the exhibit.

When creating a new project, which API implementation allows for selecting the correct API version and scaffolding the flows from the API specification?

  • A. Download RAML from Design Center
  • B. Generate a local RAML from anypoint Studio
  • C. Import RAML from local file
  • D. Import a published API

Answer: A

Explanation:
To create a new project that selects the correct API version and scaffolds the flows from the API specification, the developer should import a published API. This option allows importing an API specification that has been published to Anypoint Exchange or Design Center, and selecting a specific version of that API specification. The developer can also choose to scaffold flows based on that API specification. Reference: https://docs.mulesoft.com/apikit/4.x/apikit-4-new-project-task


NEW QUESTION # 32
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 only have Exchange Administrator permission
  • B. To configure the SLA tier for the application
  • C. To configure the SLA tier for the application and have the role of Organization Administrator, API Manager Environment Administrator, or the Manage Contacts permission
  • D. To configure the SLA tier for the application and have the Exchange Administrator permission

Answer: A

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 # 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. 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 # 34
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 # 35
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 truststore configuration and reconnection strategy for the listener
  • C. Set an appropriate reconnection strategy and use persistent connections for the listener
  • D. Set an appropriate keystore configuration 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 # 36
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. 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.
  • C. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
  • 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 # 37
A developer is working on a project that requires encrypting all data before sending it to a backend application. To accomplish this, the developer will use PGP encryption in the Mule 4 Cryptography module.
What is required to encrypt the data before sending it to the backend application?

  • A. The application needs to both the private and public keys to encrypt the data
  • B. The application needs to configure HTTPS TLS context information to encrypt the data
  • C. The application needs the private key from the backend service to encrypt the data
  • D. The application needs the public key from the backend service to encrypt the data

Answer: D

Explanation:
To encrypt the data before sending it to the backend application using PGP encryption, the application needs the public key from the backend service. PGP encryption uses a public-key cryptography system, which means that each party has a pair of keys: a public key and a private key. The public key is used to encrypt data, and the private key is used to decrypt data. Therefore, to encrypt data for a specific recipient (the backend service), the application needs to use the recipient's public key. The recipient can then use its own private key to decrypt the data. Reference: https://docs.mulesoft.com/mule-runtime/4.3/cryptography-pgp


NEW QUESTION # 38
Which statement is true when using XML SDK for creating custom message processors?

  • A. All operations are public
  • B. An XML SDK provides both inbound and outbound operations
  • C. 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
  • D. Operations can be reused in recursive calls

Answer: C

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 # 39
A developer deploys an API to CloudHub and applies an OAuth policy on API Manager. During testing, the API response is slow, so the developer reconfigures the API so that the out-of-the-box HTTP Caching policy is applied first, and the OAuth API policy is applied second.
What will happen when an HTTP request is received?

  • A. In case of a cache miss, both the OAuth and HTTP Caching policies are evaluated; then the API retrieves the data from the API implementation, and the policy does not store the data in Object Store
  • B. In case of a cache miss, only the HTTP Caching policy is evaluated; then the API retrieves the data from the API implementation, and the policy stores the data to be cached in Object Store
  • C. In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
  • D. In case of a cache hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller

Answer: C

Explanation:
When an HTTP request is received and the HTTP Caching policy is applied first, it checks if there is a cached response for that request in Object Store. If there is a cache hit, meaning that a valid cached response exists, then only the HTTP Caching policy is evaluated and the cached response is returned to the caller without invoking the OAuth policy or the API implementation. If there is a cache miss, meaning that no valid cached response exists, then both the HTTP Caching policy and the OAuth policy are evaluated before invoking the API implementation. Reference: https://docs.mulesoft.com/api-manager/2.x/http-caching-policy#policy-ordering


NEW QUESTION # 40
An API has been built to enable scheduling email provider. The front-end system does very little data entry validation, and problems have started to appear in the email that go to patients. A validate-customer'' flow is added validate the data.
What is he expected behavior of the 'validate-customer'' flow?

  • A. If all of the values are invalid the last validation error is raised:SCHEDULE:INVALID_CUSTOMER_NAME
  • B. If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised
  • C. If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid
  • D. If the appointment date and customer name are invalid, a SCHEDULE:INVALID_APPOINTMENT_DATE error is raised

Answer: B

Explanation:
The validate-customer flow uses an until-successful scope to validate each field of the customer data. The until-successful scope executes its processors until they succeed or exhausts the maximum number of retries. If any processor fails, it raises an error and stops executing the remaining processors. Therefore, if only the email address is invalid, a VALIDATION.INVALID_EMAIL error is raised and the validation of appointment date and customer name is skipped. Reference: https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope


NEW QUESTION # 41
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 200, and the response will be the JSON sent in request
  • C. The Mule flow will execute successfully with status code 204
  • D. 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.''

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 # 42
Refer to the exhibit.
What action must be performed to log all the errors raised by the VM Connector?

  • A. Nothing, as error-level events are automatically logged
  • B. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'I> inside the Logger tag
  • C. Configure <Logger level-'ERROR'/> inside the VM Connector configuration
  • D. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'/> inside the Appenders tag

Answer: D

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 # 43
Which type of cache invalidation does the Cache scope support without having to write any additional code?

  • A. Write-through invalidation
  • B. Time to live
  • C. White-behind invalidation
  • D. Notification-based 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 # 44
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. 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
  • B. Instead of using the VM Connector use <flow-ref>directly
  • C. If the two APIs use the same domain, the VM Connector can be leveraged
  • D. The VM Connector is used to inter-application communication, so it is not possible to use the VM Connector

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 # 45
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 # 46
Which plugin or dependency is required to unit test modules created with XML SDK?

  • A. XMLUnit
  • B. MUnit Extensions Maven plugin
  • C. MUnit Maven plugin
  • D. Junit

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 # 47
Mule application A is deployed to CloudHub and is using Object Store v2. Mute application B is also deployed to CloudHub.
Which approach can Mule application B use to remove values from Mule application A'S Object Store?

  • A. CloudHub Connector
  • B. Object Store Connector
  • C. CloudHub REST API
  • D. Object Store v2 REST API

Answer: D

Explanation:
To remove values from Mule application A's Object Store v2, Mule application B can use Object Store v2 REST API. This API allows performing operations on Object Store v2 resources using HTTP methods, such as GET, POST, PUT, and DELETE. Mule application B can use the DELETE method to remove values from Mule application A's Object Store v2 by specifying the object store ID and the key of the value to delete. Reference: https://docs.mulesoft.com/object-store/osv2-apis


NEW QUESTION # 48
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. XML template file, YAML configuration file
  • C. Deployable ZIP file, YAML configuration file
  • D. JSON properties file, YAML configuration file

Answer: B

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 # 49
Which statement is true when working with correlation IDS?

  • A. The Anypoint MQ Connector automatically propagates correlation IDS
  • B. The HTTP Listener regenerates correlation IDs regardless of the HTTP request
  • C. The VM Connector does not automatically propagate correction IDs
  • D. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request

Answer: D

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 # 50
A custom policy needs to be developed to intercept all cutbound HTTP requests made by Mule applications.
Which XML element must be used to intercept outbound HTTP requests?

  • A. http-policy:processor
  • B. http-policy:source
  • C. htt-policy:operation
  • D. It is not possible to intercept outgoing HTTP requests, only inbound requests

Answer: B

Explanation:
The http-policy:processor element is used to intercept outbound HTTP requests made by Mule applications. It allows customizing the request before it is sent to the target API and modifying the response after it is received from the target API. Reference: https://docs.mulesoft.com/api-manager/2.x/policy-mule4-custom-policy#policy-xml-file


NEW QUESTION # 51
......

Get Ready with Salesforce-MuleSoft-Developer-II Exam Dumps: https://pdfdumps.free4torrent.com/Salesforce-MuleSoft-Developer-II-valid-dumps-torrent.html