[2025年03月02日] 合格Salesforce MuleSoft Salesforce-MuleSoft-Developer-II試験問題集には62問があります [Q13-Q29]

Share

[2025年03月02日] 合格Salesforce MuleSoft Salesforce-MuleSoft-Developer-II試験問題集には62問があります

究極ガイドの無料準備Salesforce Salesforce-MuleSoft-Developer-II試験問題と解答


Salesforce Salesforce-MuleSoft-Developer-II 認定試験の出題範囲:

トピック出題範囲
トピック 1
  • Mule アプリケーションから本番環境対応の Anypoint プラットフォーム管理 API を公開: このトピックには、API 関連の成果物のバージョン管理の実装と、カスタムまたはすぐに使用できる API ポリシーの構成が含まれます。さらに、ポリシーを使用した API 呼び出しのサーバー側キャッシュ、API へのアクセスの要求、HTTP コールバックの実装についても説明します。
トピック 2
  • 保守可能でモジュール化された Mule アプリケーションとその Maven ビルドの実装: このトピックでは、Mule アプリケーションの Maven ビルド構成のモジュール化と最適化について説明します。Mule ランタイムへの Maven ベースの自動デプロイメントの実装について説明します。このトピックには、Maven を使用した MUnit テストの実行も含まれます。
トピック 3
  • 監視可能な Mule アプリケーションの実装: このトピックでは、Mule アプリケーションからヘルス チェック エンドポイントを公開し、効果的なログ記録を実装します。また、ログ レベルの変更、ログの集約と分析も含まれます。さらに、Mule アプリケーションの監視とメッセージ相関の実装も含まれます。
トピック 4
  • 保存時および転送中のデータのセキュリティ保護: このトピックでは、環境に依存する安全なプロパティ管理の実装について説明します。キーと証明書の作成、パッケージ化、配布について説明します。さらに、このトピックには、HTTPS 経由での API の公開と呼び出しも含まれます。
トピック 5
  • パフォーマンスと信頼性に優れた Mule アプリケーションの実装: ObjectStore の実装と、VM および AnypointMQ コネクタを使用したフォールト トレラントでパフォーマンスに優れ、追跡可能なメッセージ パッシングの確保について説明します。このトピックでは、HTTP ベースの API のフォールト トレラントな呼び出し、アサーションとメッセージの検証についても説明します。

 

質問 # 13
Which command is used to convert a JKS keystore to PKCS12?

  • A. Keytool-importkeystore -srckeystore keystore jks-srcstoretype PKCS12 -destkeystore keystore.p12 -deststoretype JKS
  • B. Keytool-importkeystore -srckeystore keystore p12-srcstoretype PKCS12 -destkeystore keystore.jks -deststoretype JKS
  • C. Keytool-importkeystore -srckeystore keystore p12-srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12
  • D. Keytool-importkeystore -srckeystore keystore jks-srcstoretype JKS -destkeystore keystore.p13 -deststoretype PKCS12

正解:C

解説:
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


質問 # 14
Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?

  • A. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
  • B. A Parallel for Each scope with each HTTP request wrapped in a Try scope
  • C. A database as a transactional outbox and an Until Successful router to retry any requests
  • D. VM queues as a reliability pattern with error handlers to roll back any requests

正解:A

解説:
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


質問 # 15
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 the email address is invalid, processing continues to see if the appointment data and customer name are also invalid
  • B. If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised
  • C. If all of the values are invalid the last validation error is raised:SCHEDULE:INVALID_CUSTOMER_NAME
  • D. If the appointment date and customer name are invalid, a SCHEDULE:INVALID_APPOINTMENT_DATE error is raised

正解:B

解説:
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


質問 # 16
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. nullPayload
  • B. originalPayload
  • C. testPayload
  • D. OS:KEY_NOT_FOUND

正解:A

解説:
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


質問 # 17
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 10 public locations with each API in its own schedule
  • B. From one private location with all 10 APIs in a single schedule
  • C. From one public location with all 10 APIs in a single schedule
  • D. From one public location with each API in its own schedule

正解:C

解説:
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


質問 # 18
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

正解:C

解説:
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


質問 # 19
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. 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.
  • B. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
  • C. In Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.
  • D. 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.

正解:A

解説:
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


質問 # 20
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 it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
  • C. 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
  • 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

正解:B

解説:
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


質問 # 21
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. Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
  • B. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
  • C. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
  • D. Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID

正解:D

解説:
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


質問 # 22
When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?

  • A. An encryption algorithm
  • B. The Public key format
  • C. A protocol
  • D. The TLS version

正解:A

解説:
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


質問 # 23
A Mule API receives a JSON payload and updates the target system with the payload. The developer uses JSON schemas to ensure the data is valid.
How can the data be validation before posting to the target system?

  • A. Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add:
    %dw 2.0
    Import.json-moduls
  • B. Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
  • C. Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
  • D. Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema

正解:D

解説:
To validate the data before posting to the target system, the developer should add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema. The JSON module provides a validate-schema operation that validates a JSON payload against a JSON schema and throws an error if the payload is invalid. Reference: https://docs.mulesoft.com/json-module/1.1/json-validate-schema


質問 # 24
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. Refer to JAR files in the code
  • B. Include the libraries writes deploying the code into the runtime
  • C. Create the Java code in your project and invoice the data from 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


質問 # 25
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 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
  • B. 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. In Design Center, open the RAML and modify baseUn to include a variable that indicates the version number
  • D. In Design Center, open the RAML and modify each operation to include the major 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


質問 # 26
When registering a client application with an existing API instance or API Group instance, what is required to manually approve or reject request access?

  • A. To only have Exchange Administrator permission
  • B. To configure the SLA tier for the application
  • C. To configure the SLA tier for the application and have the role of Organization Administrator, API Manager Environment Administrator, or the Manage Contacts permission
  • D. To configure the SLA tier for the application and have the Exchange Administrator permission

正解:A

解説:
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


質問 # 27
Which statement is true when using XML SDK for creating custom message processors?

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

正解:B

解説:
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


質問 # 28
Refer to the exhibit.
What action must be performed to log all the errors raised by the VM Connector?

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

正解:B

解説:
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


質問 # 29
......

Salesforce Certified MuleSoft Developer II練習テスト2025年最新のストレスなしでSalesforce-MuleSoft-Developer-II合格!:https://drive.google.com/open?id=1y4D30Oa7O-gUC-KRBPp5IiRjhyyOQR-z

合格させるSalesforce-MuleSoft-Developer-IIテストエンジンとPDFで完全版無料問題集:https://www.passtest.jp/Salesforce/Salesforce-MuleSoft-Developer-II-shiken.html