最適なSalesforce-MuleSoft-Developer-II試験準備問題集でSalesforce Salesforce-MuleSoft-Developer-II問題集PDFを試そう！[2025]
Salesforce Salesforce-MuleSoft-Developer-II試験受験生を確実にパスさせるSalesforce-MuleSoft-Developer-II学習問題集
質問 # 26
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 common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
- B. 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. - C. Create a Mule Plugin project
正解：C
解説：
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
質問 # 27
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 any type of queue, the message will be lost
- C. For nay type of queue, the message will be processed after the system comes online
- D. For persistent queues, the message will be processed after the system comes online
正解：D
解説：
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
質問 # 28
A mule application exposes and API for creating payments. An Operations team wants to ensure that the Payment API is up and running at all times in production.
Which approach should be used to test that the payment API is working in production?
- A. Monitor the Payment API directly sending real customer payment data
- B. Create a health check endpoint that reuses the same port number and HTTP Listener configuration as the API itself
- C. Configure the application to send health data to an external system
- D. Create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API
正解：D
質問 # 29
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 Continue to catch permanent errors like HTTP UNAUTHORIZED. - C. Put the HTTP Request inside a try scope in Unit Successful.
In the error handler, use On Error Propagate to catch permanent errors like HTTP UNAUTHORIZED. - D. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
正解：B
解説：
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
質問 # 30
Which configurations are required for HTTP Listener to enable mTLS authentication?
- A. Set an appropriate truststore configuration and reconnection strategy for the listener
- B. Set an appropriate keystore and truststore configuration 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
正解：B
解説：
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
質問 # 31
Which pattern can a web API use to notify its client of state changes as soon as they occur?
- A. Schedule Event Publisher
- B. ETL data load
- C. Shared database trigger
- D. HTTP Webhock
正解：D
解説：
A web API can use HTTP Webhook to notify its client of state changes as soon as they occur. A webhook is an HTTP callback that allows an API to send real-time notifications to another system or application when an event happens. The client registers a URL with the API where it wants to receive notifications, and then the API sends an HTTP request to that URL with information about the event. Reference: https://docs.mulesoft.com/connectors/webhook/webhook-connector
質問 # 32
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:source
- B. It is not possible to intercept outgoing HTTP requests, only inbound requests
- C. htt-policy:operation
- D. http-policy:processor
正解：A
解説：
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
質問 # 33
A heathcare customer wants to use hospital system data, which includes code that was developed using legacy tools and methods. The customer has created reusable Java libraries in order to read the data from the system.
What is the most effective way to develop an API retrieve the data from the hospital system?
- A. Include the libraries writes deploying the code into the runtime
- B. Create the Java code in your project and invoice the data from the code
- C. Refer to JAR files in the code
- D. Install libraries in a local repository and refer to it in the pm.xml file
正解：D
解説：
To develop an API that retrieves data from a hospital system using reusable Java libraries, the developer should install libraries in a local repository and refer to it in the pom.xml file. This way, the developer can use Maven to manage dependencies and invoke Java code from Mule applications using Java Module operations. Reference: https://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#add-the-java-module-to-your-project https://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#invoke-java-code
質問 # 34
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
正解：D
解説：
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
質問 # 35
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 always succeed regardless of the CA
- B. The HTTP Request operation will always fail regardless of the CA
- C. The HTTP Request operation will succeed if the CA's certificate is present in the JRE's default truststore.
- D. 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 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
質問 # 36
Which statement is true about using mutual TLS to secure an application?
- A. Mutual TLS authenticates the identity of the server before the identity of the client
- B. Mutual TLS ensures only authorized end users are allowed to access an endpoint
- C. Mutual TLS requires a hardware security module to be used
- D. Mutual TLS increases the encryption strength versus server-side TLS alone
正解：A
解説：
Mutual TLS (mTLS) is an extension of TLS that requires both parties (client and server) to present their certificates to each other during the handshake process. This way, both parties can verify each other's identity and establish a secure connection. The authentication of the server happens before the authentication of the client, as the server sends its certificate first and then requests the client's certificate. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-authentication
質問 # 37
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'/> inside the Appenders tag
- B. Configure <Logger level-'ERROR'/> inside the VM Connector configuration
- C. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'I> inside the Logger tag
- D. Nothing, as error-level events are automatically logged
正解：A
解説：
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
質問 # 38
A Mule application contain two policies Policy A and Policy A has order1, and Policy B has order 2. Policy A Policy B, and a flow are defined by he configuration below.
When a HTTP request arrives at the Mule application's endpoint, what will be the execution order?
- A. A1, B1, F1, B2, A2
- B. F1, B1, A1, A2, B2
- C. B1, A1, F1, A2, B2
- D. F1, A1, B1, B2, A2
正解：A
解説：
Based on the configuration below, when a HTTP request arrives at the Mule application's endpoint, the execution order will be A1, B1, F1, B2, A2. This is because policies are executed before and after the API implementation flow according to their order attribute. Policy A has order 1, which means it is executed first before Policy B, which has order 2. The flow is executed after both policies are executed before the flow. Then, Policy B is executed after the flow before Policy A is executed after the flow. Reference: https://docs.mulesoft.com/api-manager/2.x/policies-policy-order
質問 # 39
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 Flow Reference components inside a Try scope
Set the payload to a default value '' inside the error handler using the On Error Propagate scope - C. Add a Scatter-gather component inside a Try scope.
Set the payload to a default value 'Error' inside the error handler using the On Error Propagate scope. - D. Add Flow Reference components inside a Try scope.
Set the payload to a default value'' insider the error handler using the ON Error Continue scope
正解：A
解説：
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
質問 # 40
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 each API in its own schedule
- B. From one public location with all 10 APIs in a single schedule
- C. From 10 public locations with each API in its own schedule
- D. From one private location with all 10 APIs in a single schedule
正解：B
解説：
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
質問 # 41
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 underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
- C. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
- D. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
正解：A
解説：
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
質問 # 42
Which type of cache invalidation does the Cache scope support without having to write any additional code?
- A. Write-through invalidation
- B. White-behind invalidation
- C. Time to live
- D. Notification-based invalidation
正解：C
解説：
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
質問 # 43
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 passes
- B. The test case fails with an unexpected error type
- C. The test throws an error and does not start
- D. The test case fails with an assertion error
正解：D
解説：
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
質問 # 44
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 Continue to catch permanent errors like HTTP UNAUTHORIZED. - C. Put the HTTP Request inside a try scope in Unit Successful.
In the error handler, use On Error Propagate to catch permanent errors like HTTP UNAUTHORIZED. - D. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
正解：B
解説：
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
質問 # 45
......
完全版Salesforce-MuleSoft-Developer-II練習テスト問題集で62の別格な問題と解釈、今すぐゲットせよ：https://drive.google.com/open?id=1SsRPADcdTVV4pYpdCwqZdruA8U4KBS8F
的確で最適なアンサー模擬試験はここにある：https://www.passtest.jp/Salesforce/Salesforce-MuleSoft-Developer-II-shiken.html