Latest [Oct 31, 2024] Salesforce-MuleSoft-Developer-II Exam Dumps - Valid and Updated Dumps
Free Sales Ending Soon - 100% Valid Salesforce-MuleSoft-Developer-II Exam Dumps with 62 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 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. Settings.xml
- D. Config.yaml
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 # 24
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. White-behind invalidation
- D. Write-through 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 # 25
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 # 26
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 hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller
- B. 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
- 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 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
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 # 27
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. Import a published API
- C. Import RAML from local file
- D. Generate a local RAML from anypoint Studio
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 # 28
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 public location with each API in its own schedule
- D. From one private location with all 10 APIs in a single 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 # 29
Refer to the exhibit.
The flow name is ''implementation'' with code for the MUnit test case.
When the MUnit test case is executed, what is the expected result?
- A. The test throws an error and does not start
- B. The test case fails with an assertion error
- C. The test case fails with an unexpected error type
- D. The test case passes
Answer: B
Explanation:
Based on the code snippet and MUnit test case below, when the MUnit test case is executed, the expected result is that the test case fails with an assertion error. This is because the assert-equals processor compares two values for equality, and fails if they are not equal. In this case, the expected value is 'Hello World', but the actual value returned by the implementation flow is 'Hello Mule'. Therefore, the assertion fails and an error is thrown. Reference: https://docs.mulesoft.com/munit/2.3/assert-equals-processor
NEW QUESTION # 30
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. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
- C. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
- D. Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
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 # 31
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 Exchange Administrator permission
- 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 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 # 32
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 nay type of queue, 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 transient queues, 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 # 33
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. Deactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio
- B. Run the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager
- 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 # 34
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 only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised
- B. If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid
- C. If the appointment date and customer name are invalid, a SCHEDULE:INVALID_APPOINTMENT_DATE error is raised
- D. If all of the values are invalid the last validation error is raised:SCHEDULE:INVALID_CUSTOMER_NAME
Answer: A
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 # 35
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. It is not possible to intercept outgoing HTTP requests, only inbound requests
- C. htt-policy:operation
- D. http-policy:source
Answer: D
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 # 36
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. Configure <Logger level-'ERROR'/> inside the VM Connector configuration
- C. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'/> inside the Appenders tag
- D. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'I> inside the Logger tag
Answer: C
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 # 37
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 truststore configuration and reconnection strategy for the listener
- D. Set an appropriate keystore and truststore configuration for the listener
Answer: D
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 # 38
Which statement is true when working with correlation IDS?
- A. The Anypoint MQ Connector automatically propagates correlation IDS
- B. The VM Connector does not automatically propagate correction IDs
- C. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
- D. The HTTP Listener regenerates correlation IDs regardless of the HTTP request
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 # 39
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 public key from the backend service to encrypt the data
- D. The application needs the private key from the backend service to encrypt the data
Answer: C
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 # 40
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 # 41
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. If the two APIs use the same domain, the VM Connector can be leveraged
- B. Instead of using the VM Connector use <flow-ref>directly
- C. The VM Connector is used to inter-application communication, so it is not possible to use the VM Connector
- D. 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
Answer: A
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 # 42
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:403
- B. HTTP status code:400
- C. HTTP status code:500
- D. HTTP status code:200
Answer: A
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 # 43
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 # 44
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. Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails
- B. Remove the Put requests from the Scatter-Getter and perform them sequentially
- C. None, the flow already exhibits idempotent behavior
- D. Change the PUT requests inside the Scatter-Gather to POST requests
Answer: A
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 # 45
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. Download the common application from Naxus and copy it to the src/main/resources folder in the API
- B. Add a Maven dependency in the POM file with jar as <classifier>
- C. Copy the common application's source XML file and out it in a new flow file in the src/main/mule folder
- D. Add a Maven dependency in the PCM file with multiple-plugin as <classifier>
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 # 46
......
Salesforce-MuleSoft-Developer-II Exam Dumps - 100% Marks In Salesforce-MuleSoft-Developer-II Exam: https://www.lead2passexam.com/Salesforce/valid-Salesforce-MuleSoft-Developer-II-exam-dumps.html
Verified Salesforce-MuleSoft-Developer-II Exam Questions Certain Success: https://drive.google.com/open?id=19YVmUeGia0o-QUkbY3hjJ2gfQkbQf7Kf