MuleSoft-Integration-Architect-I 無料問題集「Salesforce Certified MuleSoft Integration Architect I」

（A）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)

（B）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

（C）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

（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

（A）Retrieve the RAML file(s) from the deployed Mule application

（B）Retrieve the WSDL file(s) from the deployed Mule application

（C）Retrieve the OpenAPI Specification file(s) from API Manager

（D）Retrieve the XML file(s) from Runtime Manager

（A）Building MUnit tests so administrators can confirm code coverage percentage during deployment

（B）Publishing the fully implemented API to Exchange so all developers can reuse the API

（C）Developing a specification so consumers can test before the implementation is built

（D）Adding global policies to the API so all developers automatically secure the implementation before coding anything

（A）A Batch Job scope to call the back-end system
An Until Successful scope containing Object Store components for long retries A dead-letter object store configured in the Mule application

（B）One or more On Error scopes to assist calling the back-end system
One or more ActiveMQ long-retry queues
A persistent dead-letter object store configured in the CloudHub Object Store service

（C）An Until Successful scope to call the back-end system
One or more ActiveMQ long-retry queues
One or more ActiveMQ dead-letter queues for manual processing

（D）One or more On Error scopes to assist calling the back-end system
An Until Successful scope containing VM components for long retries
A persistent dead-letter VM queue configured in CloudHub

（A）All routes will be rolled back

（B）Scatter Gather router cannot be part of transaction

（C）Only errored route will be rolled back

（A）Client ID Secret

（B）Federated Client Management

（C）Enterprise Security Module

（D）Federated Identity Management

（A）Policies

（B）Connectors

（C）RESTAPIs

（D）Rulesets

（A）by starting an XA transaction for each new message

（B）in a deterministic way

（C）in non-deterministic way

（D）the primary only in order to avoid duplicate processing

（A）Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically

（B）Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API

（C）Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy

（D）Build another System API that connects to the database, and refactor all the other APIs to make requests through the new System API to access the database

（A）Use the Java module

（B）Use the Transform Message component

（C）Use JAXB (XML) and Jackson (JSON) data bindings

（D）Use the WSS module

（A）Option D

（B）Option B

（C）Option C

（D）Option A

（E）In Runtime Manager, set up VPC peering between the CloudHub 2.0 private network and the on- premises data center.
In the AWS account, set up VPC peering between the AWS VPC and the CloudHub 2.0 private network.

B)
In the AWS account, attach the CloudHub 2.0 private space to an AWS transit gateway that routes from the CloudHub 2.0 private space to the on-premises data center. In Runtime Manager, configure an Anypoint VPN to route from the CloudHub 2.0 private space to the AWS VPC.

C)
In Runtime Manager, configure an Anypoint VPN to route from the CloudHub 2.0 private space to the on-premises data center. In the AWS account, attach the private..

D)
In the AWS account, attach the private space directly to the AWS VPC, In the AWS account, use an AWS transit gateway to route from the AWS VPC to the on-premises data center.

（A）Including logic within the API implementation that bypasses in locations of the back-end system in the staging environment and invoke a Mocking service that replicates typical back-end system responses Then conduct performance test using this API implementation

（B）Create a Mocking service that replicates the back-end system's production performance characteristics Then configure the API implementation to use the mocking service and conduct the performance test

（C）Conduct scaled-down performance tests in the staging environment against rate-limiting back-end system. Then upscale performance results to full production scale

（D）Use MUnit to simulate standard responses from the back-end system.
Then conduct performance test to identify other bottlenecks in the system