[2025年04月]更新のSalesforce-MuleSoft-Developer-II試験資料Salesforce学習ガイド
有効な問題最新版を試そうSalesforce-MuleSoft-Developer-IIテスト解釈Salesforce-MuleSoft-Developer-II有効な試験ガイド
Salesforce Salesforce-MuleSoft-Developer-II 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 17
A scatter-gather router is configured with four routes:Route A, B, C and D.
Route C false.
- A. Payload ['2']
- B. Error,errorMesage.payload.results ['2']
- C. Payload failures['2']
- D. Error,errorMessage,payload.failures['2']
正解：B
解説：
The result of accessing route C failure is Error,errorMessage,payload.failures['2']. This is because a scatter-gather router returns an aggregated message that contains an array of results from each route and an array of failures from each route. The failures array contains error objects with information about each failed route execution. To access route C failure, which is the third route (index 2), the developer needs to use Error.errorMessage.payload.failures['2'] expression. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-reference#scatter-gather-output
質問 # 18
A Mule application need to invoice an API hosted by an external system to initiate a process. The external API takes anywhere between one minute and 24 hours to compute its process.
Which implementation should be used to get response data from the external API after it completes processing?
- A. Use an HTTP Connector inside Async scope to invoice the API and wait for a response
- B. Use a Scheduler to check for a response every minute
- C. Expose an HTTP callback API in Mule and register it with the external system
- D. Use an HTTP Connector to invoke the API and wait for a response
正解：C
解説：
To get response data from the external API after it completes processing, the developer should expose an HTTP callback API in Mule and register it with the external system. This way, the external API can invoke the callback API with the response data when it is ready, instead of making the Mule application wait for a long time or poll for a response repeatedly. Reference: https://docs.mulesoft.com/mule-runtime/4.3/http-listener-ref#callback
質問 # 19
A system API that communicates to an underlying MySQL database is deploying to CloudHub. The DevOps team requires a readiness endpoint to monitor all system APIs.
Which strategy should be used to implement this endpoint?
- A. Use an existing resource endpoint of the API
- B. Create a dedicated endpoint that responds with the API status and reachability of the underlying systems
- C. Create a dedicated endpoint that responds with the API status only
- D. Create a dedicated endpoint that responds with the API status and health of the server
正解：B
解説：
To implement a readiness endpoint to monitor all system APIs, the developer should create a dedicated endpoint that responds with the API status and reachability of the underlying systems. This way, the DevOps team can check if the system API is ready to receive requests and if it can communicate with its backend systems without errors. Reference: https://docs.mulesoft.com/mule-runtime/4.3/deployment-strategies#readiness-probes
質問 # 20
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. originalPayload
- C. nullPayload
- D. OS:KEY_NOT_FOUND
正解：C
解説：
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
質問 # 21
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. Initialize, validate, compute, test, package, verify, install, deploy
- B. Validation, initialize, compile, test, package, install verify, 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
質問 # 22
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 all of the values are invalid the last validation error is raised:SCHEDULE:INVALID_CUSTOMER_NAME
- C. If the appointment date and customer name are invalid, a SCHEDULE:INVALID_APPOINTMENT_DATE error is raised
- D. If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid
正解：A
解説：
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
質問 # 23
Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?
- A. VM queues as a reliability pattern with error handlers to roll back any requests
- B. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
- C. A Parallel for Each scope with each HTTP request wrapped in a Try scope
- D. A database as a transactional outbox and an Until Successful router to retry any requests
正解：B
解説：
To invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures by executing compensating actions. Therefore, using a Scatter-Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/saga
質問 # 24
When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID back to the caller in the HTTP response header.
How can this be achieved?
- A. Configure a custom correlation policy
- B. 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. Enable the auto-generate CorrelationID option when scaffolding the flow
正解：C
解説：
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
質問 # 25
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.
正解：B
解説：
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
質問 # 26
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.
正解：B
解説：
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
質問 # 27
Refer to the exhibit.
What is the result if ''Insecure'' selected as part of the HTTP Listener configuration?
- A. Mutual TLS authentication will be enabled between this HTTP Listener and an HTTP client
- B. The HTTP Lister will accept any unauthenticated request
- C. The HTTP Listener will trust any certificate presented by the HTTP client
- D. The HTTP listener will only accept HTTP requests
正解：D
解説：
Based on the exhibit below, if 'Insecure' is selected as part of the HTTP Listener configuration, the HTTP listener will only accept HTTP requests. This means that no TLS context will be configured for this listener and no encryption or authentication will be applied to incoming requests. The protocol attribute of this listener will be set to HTTP instead of HTTPS. Reference: https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#insecure
質問 # 28
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 configuration and use persistent connections for the listener
- C. Set an appropriate keystore and truststore configuration for the listener
- D. Set an appropriate reconnection strategy and use persistent connections for the listener
正解：C
解説：
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
質問 # 29
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. Use the Tracing module to set logging variables with a Mapped Diagnostic Context
- B. Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
- C. Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern
- D. Use flow variables within every logger processor to log the order ID
正解：A
解説：
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
質問 # 30
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 each client subscribe directly to the exchange.
Have each client subscribe directly to the queue. - B. Publish the gate change notification to an Anypoint MC queue
Have each client subscribe directly to the queue - C. 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 - D. 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
解説：
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
質問 # 31
The HTTP Request operation raises an HTTP CONNECTIVITY error.
Which HTTP status code and body are returned to the web client?
- A. HTTP Status Code:500.
Body 'Error in processing your request - B. HTTP Status Code:500.
Body 'The HTTP CONNECTIVITY Error description - C. HTTP Status Code:500.
Body 'Error in processing your request - D. HTTP Status Code:200.
Body 'Error in processing your request
正解：A
解説：
When the HTTP Request operation raises an HTTP CONNECTIVITY error, it triggers an on-error-continue handler that sets a payload with 'Error in processing your request'. Since no status code is explicitly set in this handler, it defaults to 500 (INTERNAL SERVER ERROR). Therefore, the web client receives an HTTP response with status code 500 and body 'Error in processing your request'. Reference: https://docs.mulesoft.com/mule-runtime/4.3/error-handling#on-error-continue
質問 # 32
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. Run the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager
- B. Pass in the runtime parameter ''-Danpow.platform.gatekeeper=disabled''
- C. Deactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio
- D. Create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager
正解：B
解説：
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
質問 # 33
A developer has created the first version of an API designed for business partners to work commodity prices.
What should developer do to allow more than one major version of the same API to be exposed by the implementation?
- A. In Design Center, open the RAML and modify each operation to include the major version number
- B. In Anypoint Studio, generate scaffolding from the RAML, and then modify the flow names generated by APIKit to include a variable with the major version number
- C. In Design Center, open the RAML and modify baseUn to include a variable that indicates the version number
- D. In Anypoint Studio, generate scaffolding from the RAML, and the modify the <http:listerner> in the generated flows to include a parameter to replace the version number
正解：C
解説：
To allow more than one major version of the same API to be exposed by the implementation, the developer should modify the baseUri property in the RAML file to include a variable that indicates the version number. The baseUri property defines the base URL of the API and can include variables that are replaced with actual values when mocking or deploying the API. By using a variable for the version number, the developer can expose different versions of the API using different base URLs and avoid conflicts or confusion. Reference: https://docs.mulesoft.com/api-designer/design-modify-raml-specs#baseuri https://docs.mulesoft.com/api-manager/2.x/api-versioning
質問 # 34
......
Salesforce-MuleSoft-Developer-II試験問題と解答：https://www.passtest.jp/Salesforce/Salesforce-MuleSoft-Developer-II-shiken.html
Salesforce-MuleSoft-Developer-II実際の問題解答PDFは100%カバー率でリアル試験問題：https://drive.google.com/open?id=1y4D30Oa7O-gUC-KRBPp5IiRjhyyOQR-z