Salesforce MuleSoft-Integration-Architect-Iリアルに2024年最新のブレーン問題集で模擬試験問題集 [Q111-Q134]

Share

Salesforce MuleSoft-Integration-Architect-Iリアルに2024年最新のブレーン問題集で模擬試験問題集

MuleSoft-Integration-Architect-I試験問題 リアルなMuleSoft-Integration-Architect-I練習問題集

質問 # 111
As a part of project , existing java implementation is being migrated to Mulesoft. Business is very tight on the budget and wish to complete the project in most economical way possible.
Canonical object model using java is already a part of existing implementation. Same object model is required by mule application for a business use case. What is the best way to achieve this?

  • A. Use Anypoint exchange
  • B. Make use of Java module
  • C. Create similar model for Mule applications
  • D. Create a custom application to read Java code and make it available for Mule application

正解:B

解説:
Mule 4 is built to:
* Minimize the need for custom code.
* Avoid the need for you to know or understand Java.
However, some advanced uses cases require integration with custom Java code, such as:
* Reuse of a library, such as a tax calculation library.
* Reuse of a canonical object model that is standard in the organization.
* Execution of custom logic using Java.
Mule ref doc : https://docs.mulesoft.com/java-module/1.2/


質問 # 112
An organization has deployed both Mule and non-Mule API implementations to integrate its customer and order management systems. All the APIs are available to REST clients on the public internet.
The organization wants to monitor these APIs by running health checks: for example, to determine if an API can properly accept and process requests. The organization does not have subscriptions to any external monitoring tools and also does not want to extend its IT footprint.
What Anypoint Platform feature provides the most idiomatic (used for its intended purpose) way to monitor the availability of both the Mule and the non-Mule API implementations?

  • A. Runtime Manager
  • B. API Manager
  • C. API Functional Monitoring
  • D. Anypoint Visualizer

正解:D


質問 # 113
What is an advantage that Anypoint Platform offers by providing universal API management and Integration-Platform-as-a-Service (iPaaS) capabilities in a unified platform?

  • A. Ability to use a single control plane for both full-lifecycle AP] management and integration
  • B. Ability to use a single iPaaS to manage and integrate all API gateways
  • C. Ability to use a single iPaaS to manage all API developer portals
  • D. Ability to use a single connector to manage and integrate all APis

正解:A

解説:
Anypoint Platform offers universal API management and Integration-Platform-as-a-Service (iPaaS) capabilities in a unified platform, meaning that it provides a single control plane to manage both full-lifecycle API management and integration. This allows organizations to easily manage their APIs and integrations, as well as deploy APIs and integrations quickly and efficiently. According to the MuleSoft Certified Integration Architect - Level 1 Course Book, "Anypoint Platform provides a unified platform for managing, deploying, and monitoring both API and integration solutions, allowing organizations to quickly and easily build and manage their APIs and integrations."


質問 # 114
How should the developer update the logging configuration in order to enable this package specific debugging?

  • A. In the Mule application's log4j2.xml file, add an AsyncLogger element with name property set to org.apache.cxf and level set to DEBUG, then redeploy the Mule application in the CloudHub production environment
  • B. In the Mule application's log4j2.xmI file, change the root logger's level property to DEBUG, then redeploy the Mule application to the CloudHub production environment
  • C. In Anypoint Runtime Manager, in the Deployed Application Properties tab for the Mule application, add a line item with DEBUG level for package org.apache.cxf and apply the changes
  • D. In Anypoint Monitoring, define a logging search query with class property set to org.apache.cxf and level set to DEBUG

正解:D


質問 # 115
An organization has decided on a cloud migration strategy to minimize the organization's own IT resources. Currently the organization has all of its new applications running on its own premises and uses an on-premises load balancer that exposes all APIs under the base URL (https://api.rutujar.com).
As part of migration strategy, the organization is planning to migrate all of its new applications and load balancer CloudHub.
What is the most straightforward and cost-effective approach to Mule application deployment and load balancing that preserves the public URL's?

  • A. For each migrated Mule application, deploy an API proxy application to Cloudhub with all traffic to the mule applications routed through a Cloud Hub Dedicated load balancer (DLB) Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub dedicated load balancer Apply mapping rules in DLB to map each API proxy application who is responding new application
  • B. Deploy the Mule application to Cloudhub
    Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub shared load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications
  • C. Deploy the Mule application to Cloudhub
    Create a CNAME record for base URL( httpsr://api.rutujar.com) in the Cloudhub shared load balancer that points to the A record of theon-premises load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications
  • D. Deploy the Mule application to Cloudhub
    Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the Cloudhub dedicated load balancer Apply mapping rules in DLB to map URLto their corresponding Mule applications

正解:D


質問 # 116
A Mule application is being designed To receive nightly a CSV file containing millions of records from an external vendor over SFTP, The records from the file need to be validated, transformed. And then written to a database. Records can be inserted into the database in any order.
In this use case, what combination of Mule components provides the most effective and performant way to write these records to the database?

  • A. Use a Parallel for Each scope to Insert records one by one into the database
  • B. Use a Batch job scope to bulk insert records into the database.
  • C. Use a Scatter-Gather to bulk insert records into the database
  • D. Use a DataWeave map operation and an Async scope to insert records one by one into the database.

正解:B

解説:
Correct answer is Use a Batch job scope to bulk insert records into the database
* Batch Job is most efficient way to manage millions of records.
A few points to note here are as follows :
Reliability: If you want reliabilty while processing the records, i.e should the processing survive a runtime crash or other unhappy scenarios, and when restarted process all the remaining records, if yes then go for batch as it uses persistent queues.
Error Handling: In Parallel for each an error in a particular route will stop processing the remaining records in that route and in such case you'd need to handle it using on error continue, batch process does not stop during such error instead you can have a step for failures and have a dedicated handling in it.
Memory footprint: Since question said that there are millions of records to process, parallel for each will aggregate all the processed records at the end and can possibly cause Out Of Memory.
Batch job instead provides a BatchResult in the on complete phase where you can get the count of failures and success. For huge file processing if order is not a concern definitely go ahead with Batch Job


質問 # 117
Cloud Hub is an example of which cloud computing service model?

  • A. Software as a Service (SaaS)
  • B. Monitoring as a Service (MaaS)
  • C. Infrastructure as a Service (laaS)
  • D. Platform as a Service (PaaS)

正解:D


質問 # 118
To implement predictive maintenance on its machinery equipment, ACME Tractors has installed thousands of IoT sensors that will send data for each machinery asset as sequences of JMS messages, in near real-time, to a JMS queue named SENSOR_DATA on a JMS server. The Mule application contains a JMS Listener operation configured to receive incoming messages from the JMS servers SENSOR_DATA JMS queue. The Mule application persists each received JMS message, then sends a transformed version of the corresponding Mule event to the machinery equipment back-end systems.
The Mule application will be deployed to a multi-node, customer-hosted Mule runtime cluster. Under normal conditions, each JMS message should be processed exactly once.
How should the JMS Listener be configured to maximize performance and concurrent message processing of the JMS queue?

  • A. Set numberOfConsumers = 1
    Set primaryNodeOnly = true
  • B. Set numberOfConsumers to a value greater than one
    Set primaryNodeOnly = true
  • C. Set numberOfConsumers = 1
    Set primaryNodeOnly = false
  • D. Set numberOfConsumers to a value greater than one
    Set primaryNodeOnly = false

正解:D


質問 # 119
Refer to the exhibit.

An organization deploys multiple Mule applications to the same customer -hosted Mule runtime. Many of these Mule applications must expose an HTTPS endpoint on the same port using a server-side certificate that rotates often.
What is the most effective way to package the HTTP Listener and package or store the server-side certificate when deploying these Mule applications, so the disruption caused by certificate rotation is minimized?

  • A. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION
  • B. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing It from all Mule applications that need to expose an HTTPS endpoint. Package the server-side certificate in the SAME Mule DOMAIN project Go to Set
  • C. Package an HTTPS Listener configuration In all Mule APPLICATIONS that need to expose an HTTPS endpoint Package the server-side certificate in a NEW Mule DOMAIN project
  • D. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint Package the server-side certificate in ALL Mule APPLICATIONS that need to expose an HTTPS endpoint

正解:A

解説:
In this scenario, both A & C will work, but A is better as it does not require repackage to the domain project at all.
Correct answer is Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION.
What is Mule Domain Project?
* A Mule Domain Project is implemented to configure the resources that are shared among different projects. These resources can be used by all the projects associated with this domain. Mule applications can be associated with only one domain, but a domain can be associated with multiple projects. Shared resources allow multiple development teams to work in parallel using the same set of reusable connectors. Defining these connectors as shared resources at the domain level allows the team to: - Expose multiple services within the domain through the same port. - Share the connection to persistent storage. - Share services between apps through a well-defined interface. - Ensure consistency between apps upon any changes because the configuration is only set in one place.
* Use domains Project to share the same host and port among multiple projects. You can declare the http connector within a domain project and associate the domain project with other projects. Doing this also allows to control thread settings, keystore configurations, time outs for all the requests made within multiple applications. You may think that one can also achieve this by duplicating the http connector configuration across all the applications. But, doing this may pose a nightmare if you have to make a change and redeploy all the applications.
* If you use connector configuration in the domain and let all the applications use the new domain instead of a default domain, you will maintain only one copy of the http connector configuration. Any changes will require only the domain to the redeployed instead of all the applications.
You can start using domains in only three steps:
1) Create a Mule Domain project
2) Create the global connector configurations which needs to be shared across the applications inside the Mule Domain project
3) Modify the value of domain in mule-deploy.properties file of the applications

Use a certificate defined in already deployed Mule domain Configure the certificate in the domain so that the API proxy HTTPS Listener references it, and then deploy the secure API proxy to the target Runtime Fabric, or on-premises target. (CloudHub is not supported with this approach because it does not support Mule domains.)


質問 # 120
An organization is designing Mule application which connects to a legacy backend. It has been reported that backend services are not highly available and experience downtime quite often. As an integration architect which of the below approach you would propose to achieve high reliability goals?

  • A. On Error Continue scope to be used to call in case of error again
  • B. Create a batch job with all requests being sent to backend using that job as per the availability of backend API's
  • C. Until Successful scope can be implemented while calling backend API's
  • D. Alerts can be configured in Mule runtime so that backend team can be communicated when services are down

正解:C

解説:
Correct answer is Untill Successful scope can be implemented while calling backend API's The Until Successful scope repeatedly triggers the scope's components (including flow references) until they all succeed or until a maximum number of retries is exceeded The scope provides option to control the max number of retries and the interval between retries The scope can execute any sequence of processors that may fail for whatever reason and may succeed upon retry


質問 # 121
A new Mule application under development must implement extensive data transformation logic. Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.
The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.
What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?

  • A. Implement transformation logic in the new Mute application using DataWeave, replicating the transformation logic of existing transformation services
  • B. Extend the existing transformation services with new transformation logic and Invoke them from the new Mule application
  • C. Implement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible
  • D. Implement and expose all transformation logic as mlaoservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application

正解:C

解説:
Correct answer is Implement transformation logic in the new Mule application using DataWeave, invoking existing transformation services when possible. * The key here minimal testing effort, "Extend existing transformation logic" is not a feasible option because additional functionality is highly specific to the new Mule application so it should not be a part of commonly used functionality. So this option is ruled out. * "Implement transformation logic in the new Mule application using DataWeave, replicating the transformation logic of existing transformation services" Replicating the transformation logic of existing transformation services will cause duplicity of code. So this option is ruled out. * "Implement and expose all transformation logic as microservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application" as question specifies that the transformation is app specific and wont be used outside


質問 # 122
Refer to the exhibit.

A Mule 4 application has a parent flow that breaks up a JSON array payload into 200 separate items, then sends each item one at a time inside an Async scope to a VM queue.
A second flow to process orders has a VM Listener on the same VM queue. The rest of this flow processes each received item by writing the item to a database.
This Mule application is deployed to four CloudHub workers with persistent queues enabled.
What message processing guarantees are provided by the VM queue and the CloudHub workers, and how are VM messages routed among the CloudHub workers for each invocation of the parent flow under normal operating conditions where all the CloudHub workers remain online?

  • A. ALL Item VM messages are processed AT LEAST ONCE by the SAME CloudHub worker where the parent flow was invoked This one CloudHub worker processes ALL 200 item VM messages
  • B. EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages
  • C. EACH item VM message is processed AT MOST ONCE by ONE CloudHub worker, with workers chosen in a deterministic round-robin fashion Each of the four CloudHub workers can be expected to process 1/4 of the Item VM messages (about 50 items)
  • D. ALL item VM messages are processed AT MOST ONCE by ONE ARBITRARY CloudHub worker This one CloudHub worker processes ALL 200 item VM messages

正解:B

解説:
Correct answer is EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker. Each of the four CloudHub workers can be expected to process some item VM messages In Cloudhub, each persistent VM queue is listened on by every CloudHub worker - But each message is read and processed at least once by only one CloudHub worker and the duplicate processing is possible - If the CloudHub worker fails , the message can be read by another worker to prevent loss of messages and this can lead to duplicate processing - By default , every CloudHub worker's VM Listener receives different messages from VM Queue Referenece: https://dzone.com/articles/deploying-mulesoft-application-on-1-worker-vs-mult


質問 # 123
An IT integration delivery team begins a project by gathering all of the requirements, and proceeds to execute the remaining project activities as sequential, non-repeating phases.
Which IT project delivery methodology is this team following?

  • A. Agile
  • B. Kanban
  • C. Waterfall
  • D. Scrum

正解:C


質問 # 124
An organization is designing a mule application to support an all or nothing transaction between serval database operations and some other connectors so that they all roll back if there is a problem with any of the connectors Besides the database connector , what other connector can be used in the transaction.

  • A. VM
  • B. SFTP
  • C. Anypoint MQ
  • D. ObjectStore

正解:A

解説:
Correct answer is VM VM support Transactional Type. When an exception occur, The transaction rolls back to its original state for reprocessing. This feature is not supported by other connectors.
Here is additional information about Transaction management:


質問 # 125
Refer to the exhibit.

A Mule application has an HTTP Listener that accepts HTTP DELETE requests. This Mule application Is deployed to three CloudHub workers under the control of the CloudHub Shared Load Balancer.
A web client makes a sequence of requests to the Mule application's public URL.
How is this sequence of web client requests distributed among the HTTP Listeners running in the three CloudHub workers?

  • A. Each request is routed (scattered) to ALL three CloudHub workers at the same time
  • B. Each request is routed to the PRIMARY CloudHub worker in the PRIMARY Availability Zone (AZ)
  • C. Each request Is routed to ONE ARBiTRARY CloudHub worker out of ALL three CloudHub workers
  • D. Each request is routed to ONE ARBiTRARY CloudHub worker in the PRIMARY Availability Zone (AZ)

正解:C

解説:
Correct behavior is Each request is routed to ONE ARBITRARY CloudHub worker out of ALL three CloudHub workers


質問 # 126
An organization plans to migrate all its Mule applications to Runtime Fabric (RTF). Currently, all Mule applications have been deployed to CloudHub using automated CI/CD scripts.
What steps should be taken to properly migrate the applications from CloudHub to RTF, while keeping the same automated CI/CD deployment strategy?

  • A. runtimeFabric command-line parameter should be added to the CI/CD deployment scripts.
  • B. A runtimefFabricDeployment profile should be added to Mule configuration properties YAML files in all the Mule applications.
    CI/CD scripts must be modified to use the new configuration properties.
  • C. A runtimefabric dependency should be added as a mule-plugin to the pom.xml file in all the Mule applications.
  • D. The pom.xml and Mule configuration YAML files can remain unchanged in each Mule application.
    A --runtimeFabric command-line parameter should be added to the CI/CD deployment scripts
  • E. runtimefabricDeployment profile should be added to the pom.xml file in all the Mule applications. CI/CD scripts must be modified to use the new RTF profile.

正解:C


質問 # 127
A Mule application name Pub uses a persistence object store. The Pub Mule application is deployed to Cloudhub and it configured to use Object Store v2.
Another Mule application name sub is being developed to retrieve values from the Pub Mule application persistence object Store and will also be deployed to cloudhub.
What is the most direct way for the Sub Mule application to retrieve values from the Pub Mule application persistence object store with the least latency?

  • A. Use an Anypoint MQ connector configured to directly access the Pub Mule application persistence object store
  • B. Use an object store connector configured to access the Pub Mule application persistence object store
  • C. Use a VM connector configured to directly access the persistence queue of the Pub Mule application persistence object store.
  • D. Use the Object store v2 REST API configured to access the Pub Mule application persistence object store.

正解:D

解説:
* The Object Store V2 API enables API access to Anypoint Platform Object Store v2.
* You can configure a Mule app to use the Object Store REST API to store and retrieve values from an object store in another Mule app. However, Object Store v2 is not designed for app-to-app communication. To share data between two Mule4 apps, use a queue in Anypoint MQ.
* The Object Store v2 APIs enable you to use REST to perform the following:
- Retrieve a list of object stores and keys associated with an application.
- Store and retrieve key-value pairs in an object store.
- Delete key-value pairs from an object store.
- Retrieve Object Store usage statistics for your organization.
- Object Store provides these APIs:
Object Store API
Object Store Stats API
Reference:
Additional Info:
When to use Object Store and when to use VM


質問 # 128
An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime duster. The Mule application uses a Listener operation of a JMS connector to receive incoming messages from a JMS queue.
How are the messages consumed by the Mule application?

  • A. Regardless of the Listener operation configuration, all messages are consumed by ALL cluster nodes
  • B. Regardless of the Listener operation configuration, all messages are consumed by ONLY the primary cluster node
  • C. Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node
  • D. Depending on the JMS provider's configuration, either all messages are consumed by ONLY the primary cluster node or else ALL messages are consumed by ALL cluster nodes

正解:C

解説:
Correct answer is Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node For applications running in clusters, you have to keep in mind the concept of primary node and how the connector will behave. When running in a cluster, the JMS listener default behavior will be to receive messages only in the primary node, no matter what kind of destination you are consuming from. In case of consuming messages from a Queue, you'll want to change this configuration to receive messages in all the nodes of the cluster, not just the primary.
This can be done with the primaryNodeOnly parameter:
<jms:listener config-ref="config" destination="${inputQueue}" primaryNodeOnly="false"/>


質問 # 129
According to the Internet Engineering Task Force (IETF), which supporting protocol does File Transfer Protocol (FTP) use for reliable communication?

  • A. B Transmission Control Protocol (TCP)
  • B. A Secure Sockets Layer (SSL)
  • C. Hypertext Transfer Protocol (HTTP)
  • D. Lightweight Directory Access Protocol (LDAP)

正解:A


質問 # 130
What metrics about API invocations are available for visualization in custom charts using Anypoint Analytics?

  • A. Request size, number of requests, response size, response time
  • B. Request size, number of requests, JDBC Select operation result set size
  • C. Request size, number of requests, JDBC Select operation response time
  • D. Request size, request HTTP verbs, response time

正解:A

解説:
Correct answer is Request size, number of requests, response size, response time Analytics API Analytics can provide insight into how your APIs are being used and how they are performing. From API Manager, you can access the Analytics dashboard, create a custom dashboard, create and manage charts, and create reports. From API Manager, you can get following types of analytics: - API viewing analytics - API events analytics - Charted metrics in API Manager It can be accessed using: http://anypoint.mulesoft.com/analytics API Analytics provides a summary in chart form of requests, top apps, and latency for a particular duration.
The custom dashboard in Anypoint Analytics contains a set of charts for a single API or for all APIs Each chart displays various API characteristics
- Requests size: Line chart representing size of requests in KBs
- Requests : Line chart representing number of requests over a period
- Response size : Line chart representing size of response in KBs
- Response time :Line chart representing response time in ms
* To check this, You can go to API Manager > Analytics > Custom Dashboard > Edit Dashboard > Create Chart > Metric

Reference:
Additional Information:
The default dashboard contains a set of charts
- Requests by date: Line chart representing number of requests
- Requests by location: Map chart showing the number of requests for each country of origin
- Requests by application: Bar chart showing the number of requests from each of the top five registered applications
- Requests by platform: Ring chart showing the number of requests broken down by platform


質問 # 131
How are the API implementation , API client, and API consumer combined to invoke and process an API ?

  • A. The API client creates an API consumer which sends API invocations to an API such that they are processed by API implementation
  • B. The API consumer creates an API implementation , which receives API invocations from an API such that they are processed for an API client
  • C. An API client creates an API consumer, which receives API invocation from an API such that they are processed for an API implementation
  • D. The API consumer creates an API client which sends API invocations to an API such that they are processed by an API implementation

正解:C

解説:
The API consumer creates an API client which sends API invocations to an API such that they are processed by an API implementation This is based on below definitions API client * An application component * that accesses a service * by invoking an API of that service - by definition of the term API over HTTP API consumer * A business role, which is often assigned to an individual * that develops API clients, i.e., performs the activities necessary for enabling an API client to invoke APIs API implementation * An application component * that implements the functionality


質問 # 132
As an enterprise architect, what are the two reasons for which you would use a canonical data model in the new integration project using Mulesoft Anypoint platform ( choose two answers )

  • A. To have consistent data structure aligned in processes
  • B. To incorporate industry standard data formats
  • C. Because the model isolates the back and systems and support mule applications from change
  • D. To isolate areas within a bounded context
  • E. There are multiple canonical definitions of each data type

正解:A、D


質問 # 133
The AnyAirline organization's passenger reservations center is designing an integration solution that combines invocations of three different System APIs (bookFlight, bookHotel, and bookCar) in a business transaction. Each System API makes calls to a single database.
The entire business transaction must be rolled back when at least one of the APIs fails.
What is the most idiomatic (used for its intended purpose) way to integrate these APIs in near real-time that provides the best balance of consistency, performance, and reliability?

  • A. Implement local transactions in each API implementation
    Coordinate between the API implementations using a Saga pattern
    Apply various compensating actions depending on where a failure occurs
  • B. Implement local transactions within each API implementation
    Configure each API implementation to also participate in the same eXtended Architecture (XA) transaction Implement caching in each API implementation to improve performance
  • C. Implement eXtended Architecture (XA) transactions between the API implementations Coordinate between the API implementations using a Saga pattern Implement caching in each API implementation to improve performance
  • D. Implement an eXtended Architecture (XA) transaction manager in a Mule application using a Saga pattern Connect each API implementation with the Mule application using XA transactions Apply various compensating actions depending on where a failure occurs

正解:A


質問 # 134
......

厳密検証されたMuleSoft-Integration-Architect-I試験問題集と解答で無料提供のMuleSoft-Integration-Architect-I問題と正解付き:https://www.passtest.jp/Salesforce/MuleSoft-Integration-Architect-I-shiken.html

あなたを合格させるMuleSoft-Integration-Architect-I問題集無料で最新のSalesforce練習テスト:https://drive.google.com/open?id=13pKOSBS8qveX2xx-iljV_5hLoObMt4JV