Pass Your Salesforce Exam with Salesforce-MuleSoft-Developer-II Exam Dumps (Updated 62 Questions)
Salesforce-MuleSoft-Developer-II Exam Dumps - Salesforce Practice Test Questions
Salesforce Salesforce-MuleSoft-Developer-II Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 27
Which command is used to convert a JKS keystore to PKCS12?
- A. Keytool-importkeystore -srckeystore keystore p12-srcstoretype PKCS12 -destkeystore keystore.jks -deststoretype JKS
- B. Keytool-importkeystore -srckeystore keystore jks-srcstoretype PKCS12 -destkeystore keystore.p12 -deststoretype JKS
- C. Keytool-importkeystore -srckeystore keystore jks-srcstoretype JKS -destkeystore keystore.p13 -deststoretype PKCS12
- D. Keytool-importkeystore -srckeystore keystore p12-srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12
Answer: D
Explanation:
To convert a JKS keystore to PKCS12, the developer needs to use the keytool-importkeystore command with the following options: -srckeystore keystore.jks -srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12. This command imports all entries from a source JKS keystore (keystore.jks) into a destination PKCS12 keystore (keystore.p12). Reference: https://docs.oracle.com/en/java/javase/11/tools/keytool.html#GUID-5990A2E4-78E3-47B7-AE75-6D1826259549
NEW QUESTION # 28
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. Config.yaml
- B. Settings.xml
- C. Pom.xml
- D. Mule.artificact.json
Answer: C
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 # 29
When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?
- A. The Public key format
- B. The TLS version
- C. An encryption algorithm
- D. A protocol
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 # 30
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. Use ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases
- C. Chain together the test suites and test cases for Flow-1 and Flow-2
- 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 # 31
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 # 32
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 APlkit Console to receive all incoming RESTful operation requests.
- C. The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
- D. Northing because flowRef is an optional attribute which can be passed runtime
Answer: C
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 # 33
Which statement is true when using XML SDK for creating custom message processors?
- A. All operations are public
- B. 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
- C. An XML SDK provides both inbound and outbound operations
- D. Operations can be reused in recursive calls
Answer: B
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 # 34
Refer to the exhibit.
What action must be performed to log all the errors raised by the VM Connector?
- A. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'I> inside the Logger tag
- B. Nothing, as error-level events are automatically logged
- C. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'/> inside the Appenders tag
- D. Configure <Logger level-'ERROR'/> inside the VM Connector configuration
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 # 35
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. Pass in the runtime parameter ''-Danpow.platform.gatekeeper=disabled''
- B. Create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager
- C. Deactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio
- D. Run the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager
Answer: A
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 # 36
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. Generate a local RAML from anypoint Studio
- D. Import RAML from local file
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 # 37
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 MQ exchanhe.
Create different Anypoint MQ queues meant for each of the other subscribing systems.Bind the exchange with each of the queues. - D. Publish the gate change notification to an Anypoint MC queue
Have each client subscribe directly to the queue
Answer: C
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 # 38
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. Settings, xml
- D. A Bill of Materials (BOM) parent pm
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 # 39
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. Validation, initialize, compile, test, package, install verify, deploy
- B. Initialize, validate, compute, test, package, verify, install, deploy
- C. Validate, initialize, compile, package, test, install, verify, verify, deploy
- D. Validate, initialize, compile, test package, verify, install, deploy
Answer: D
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 # 40
Refer to the exhibit.
What is the result of the Mule Maven Plugin configuration of the value of property its,keystorePassoword in CloudHub 2.0?
- A. CloudHub encrypts the value
- B. Anypoint Studio secures the value
- C. Runtime Manager masks the value
- D. The Mule server encrypts the value
Answer: C
Explanation:
The result of the Mule Maven Plugin configuration of the value of property its,keystorePassword in CloudHub 2.0 is that Runtime Manager masks the value. This means that Runtime Manager hides or obscures the value from anyone who views it in Runtime Manager or Anypoint Platform. Reference: https://docs.mulesoft.com/runtime-manager/runtime-manager-agent-for-mule4#properties-tab
NEW QUESTION # 41
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. testPayload
- B. OS:KEY_NOT_FOUND
- C. nullPayload
- D. originalPayload
Answer: C
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 # 42
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. XML template file, YAML configuration file
- C. JSON properties file, XML template 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 # 43
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. htt-policy:operation
- B. http-policy:processor
- C. http-policy:source
- D. It is not possible to intercept outgoing HTTP requests, only inbound requests
Answer: C
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 # 44
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 appointment date and customer name are invalid, a SCHEDULE:INVALID_APPOINTMENT_DATE 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 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 # 45
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 case fails with an assertion error
- B. The test case passes
- C. The test case fails with an unexpected error type
- D. The test throws an error and does not start
Answer: A
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 # 46
Which statement is true when working with correlation IDS?
- A. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
- B. The VM Connector does not automatically propagate correction IDs
- C. The HTTP Listener regenerates correlation IDs regardless of the HTTP request
- D. The Anypoint MQ Connector automatically propagates correlation IDS
Answer: A
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 # 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: D
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
The flow is invoicing a target API. The API's protocol is HTTPS. The TLS configuration in the HTTP Request Configuration global element is set to None. A web client submits a request to http:localhost:8081/vehicles.
If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP Request operation when the flow executes?
- A. The HTTP Request operation will succeed if the CA's certificate is present in the JRE's default truststore.
- B. The HTTP Request operation will succeed if the CA'S certificate is present in the JRE's default keystore
- C. The HTTP Request operation will always fail regardless of the CA
- D. The HTTP Request operation will always succeed regardless of the CA
Answer: A
Explanation:
The HTTP Request operation will use the default truststore of the JRE to validate the certificate of the target API. If the CA's certificate is present in the truststore, the operation will succeed. Otherwise, it will fail with a handshake exception. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#tls-default
NEW QUESTION # 49
A Mule application for processing orders must log the order ID for every log message output.
What is a best practice to enrich every log message with the order ID?
- A. Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
- B. Use the Tracing module to set logging variables with a Mapped Diagnostic Context
- C. Use flow variables within every logger processor to log the order ID
- D. Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern
Answer: B
Explanation:
To enrich every log message with the order ID, the developer should use the Tracing module to set logging variables with a Mapped Diagnostic Context (MDC). The Tracing module allows adding custom key-value pairs to log messages using MDC variables. The developer can use Set Logging Variables operation to set the order ID as an MDC variable and then use it in any logger processor within the same thread or event. Reference: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#set-logging-variables
NEW QUESTION # 50
When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID back to the caller in the HTTP response header.
How can this be achieved?
- A. Enable the auto-generate CorrelationID option when scaffolding the flow
- B. NO action is needed as the correlation ID is returned to the caller in the response header by default
- C. Enable the CorrelationID checkbox in the HTTP Listener configuration
- D. Configure a custom correlation policy
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 # 51
......
New Real Salesforce-MuleSoft-Developer-II Exam Dumps Questions: https://drive.google.com/open?id=1jsVoCTr98go8Z2AabconXEBvhl5Vyve5
Pass Your Salesforce-MuleSoft-Developer-II Exam Easily with Accurate PDF Questions: https://www.prep4sureexam.com/Salesforce-MuleSoft-Developer-II-dumps-torrent.html