試験高合格率保証2024年11月20日 MuleSoft-Integration-Architect-I試験問題と正確な回答！
テストエンジン練習問題MuleSoft-Integration-Architect-I有効最新の問題集
質問 # 36
An organization's IT team follows an API-led connectivity approach and must use Anypoint Platform to implement a System AP\ that securely accesses customer dat a. The organization uses Salesforce as the system of record for all customer data, and its most important objective is to reduce the overall development time to release the System API.
The team's integration architect has identified four different approaches to access the customer data from within the implementation of the System API by using different Anypoint Connectors that all meet the technical requirements of the project.
- A. Use the Anypoint Connector for HTTP to connect to the Salesforce APIs to directly access the customer data
- B. Use the Anypoint Connector for Salesforce to connect to the Salesforce APIs to directly access the customer data
- C. Use the Anypoint Connector tor FTP to download a file containing a recent near-real time extract of the customer data
- D. Use the Anypoint Connector for Database to connect to a MySQL database to access a copy of the customer data
正解：B
質問 # 37
Following MuleSoft best practices, what MuleSoft runtime deployment option best meets the company's goals to begin its digital transformation journey?
- A. Runtime Fabric on VMs/bare metal
- B. Customer-hosted runtimes provisioned by a MuleSoft services partner
- C. Customer-hosted self-provisioned runtimes
- D. CloudHub runtimes
正解：A
質問 # 38
A company is designing a mule application to consume batch data from a partner's ftps server The data files have been compressed and then digitally signed using PGP.
What inputs are required for the application to securely consumed these files?
- A. ATLS context Key Store requiring the private key and certificate for the company PGP public key of partner PGP private key for the company
- B. TLS context trust or containing a public certificate for the ftps server The FTP username and password The PGP public key of the partner
- C. The PGP public key of the partner
The PGP private key for the company
The FTP username and password - D. ATLS context first store containing a public certificate for partner ftps server and the PGP public key of the partner TLS contact Key Store containing the FTP credentials
正解：C
質問 # 39
What is not true about Mule Domain Project?
- A. This allows Mule applications to share resources
- B. Only available Anypoint Runtime Fabric
- C. Send events (messages) to other Mule applications using VM queues
- D. Expose multiple services within the Mule domain on the same port
正解：B
解説：
* Mule Domain Project is ONLY available for customer-hosted Mule runtimes, but not for Anypoint Runtime Fabric
* Mule domain project is available for Hybrid and Private Cloud (PCE). Rest all provide application isolation and can't support domain project.
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
質問 # 40
A Mule application contains a Batch Job scope with several Batch Step scopes. The Batch Job scope is configured with a batch block size of 25.
A payload with 4,000 records is received by the Batch Job scope.
When there are no errors, how does the Batch Job scope process records within and between the Batch Step scopes?
- A. The Batch Job scope processes multiple record blocks in parallel
Each Batch Step scope is invoked with a batch of 25 records in the payload of the received Mule event For each Batch Step scope, all 4000 records are processed in parallel Individual records can jump ahead to the next Batch Step scope before the rest of the records finish processing in the current Batch Step scope - B. The Batch Job scope processes each record block sequentially, one at a time Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one at a time All 4000 records must be completed before the blocks of records are available to the next Batch Step scope
- C. The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed in parallel All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope
- D. The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one record at a time All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope
正解：C
質問 # 41
An organization has implemented the cluster with two customer hosted Mule runtimes is hosting an application.
This application has a flow with a JMS listener configured to consume messages from a queue destination. As an integration architect can you advise which JMS listener configuration must be used to receive messages in all the nodes of the cluster?
- A. Use the parameter primaryNodeOnly= "false" on the JMS listener with a shared subscription
- B. Use the parameter primaryNodeOnly= "true" on the JMS listener
- C. Use the parameter primaryNodeOnly= "true" on the JMS listener with a nonshared subscription
- D. Use the parameter primaryNodeOnly= "false" on the JMS listener
正解：D
質問 # 42
According to MuleSoft, a synchronous invocation of a RESTful API using HTTP to get an individual customer record from a single system is an example of which system integration interaction pattern?
- A. Request-Reply
- B. Multicast
- C. One-way
- D. Batch
正解：A
質問 # 43
According to MuleSoft, what Action should an IT organization take regarding its technology assets in order to close the IT delivery.
- A. Create weekly meetings that all members of IT attend to present justification and request approval to use existing assets
- B. Make assets easily discoverable via a central repository
- C. Hire additional staff to meet the demand for asset creation required for approved projects and timelines
- D. Focus project delivery efforts on custom assets that meet the specific requirements of each individual line of business
正解：D
質問 # 44
Refer to the exhibit.
A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.
HTTP clients send HTTP requests directly to individual cluster nodes.
What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has railed, but before that node is restarted?
- A. Database polling stops All HTTP requests are rejected
- B. Database polling stops All HTTP requests continue to be accepted
- C. Database polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency
- D. Database polling continues Only HTTP requests sent to the remaining node continue to be accepted
正解：D
解説：
Correct answer is Database polling continues Only HTTP requests sent to the remaining node continue to be accepted. : Architecture descripted in the question could be described as follows.When node 1 is down , DB polling will still continue via node 2 . Also requests which are coming directly to node 2 will also be accepted and processed in BAU fashion. Only thing that wont work is when requests are sent to Node 1 HTTP connector. The flaw with this architecture is HTTP clients are sending HTTP requests directly to individual cluster nodes. By default, clustering Mule runtime engines ensures high system availability. If a Mule runtime engine node becomes unavailable due to failure or planned downtime, another node in the cluster can assume the workload and continue to process existing events and messages
質問 # 45
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. Until Successful scope can be implemented while calling backend API's
- B. Create a batch job with all requests being sent to backend using that job as per the availability of backend API's
- C. Alerts can be configured in Mule runtime so that backend team can be communicated when services are down
- D. On Error Continue scope to be used to call in case of error again
正解：A
解説：
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
質問 # 46
What are two reasons why a typical MuleSoft customer favors a MuleSoft-hosted Anypoint Platform runtime plane over a customer-hosted runtime for its Mule application deployments? (Choose two.)
- A. Reduced IT operations effort
- B. Reduced time-to-market for the first application
- C. Increased application throughput
- D. Reduced application latency
- E. Increased application isolation
正解：A、B
質問 # 47
According to MuleSoft, which system integration term describes the method, format, and protocol used for communication between two system?
- A. interaction
- B. Component
- C. Message
- D. Interface
正解：D
質問 # 48
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, invoking existing transformation services when possible
- B. Extend the existing transformation services with new transformation logic and Invoke them from the new Mule application
- C. 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
- D. Implement transformation logic in the new Mute application using DataWeave, replicating the transformation logic of existing transformation services
正解：A
解説：
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
質問 # 49
Refer to the exhibit.
One of the backend systems invoked by an API implementation enforces rate limits on the number of requests a particular client can make. Both the backend system and the API implementation are deployed to several non-production environments in addition to production.
Rate limiting of the backend system applies to all non-production environments. The production environment, however, does NOT have any rate limiting.
What is the most effective approach to conduct performance tests of the API implementation in a staging (non-production) environment?
- A. Conduct scaled-down performance tests in the staging environment against the rate limited backend system then upscale performance results to full production scale
- B. Include logic within the API implementation that bypasses invocations of the backend system in a performance test situation. Instead invoking local stubs that replicate typical backend system responses then conduct performance tests using this API Implementation
- C. Use MUnit to simulate standard responses from the backend system then conduct performance tests to identify other bottlenecks in the system
- D. Create a mocking service that replicates the backend system's production performance characteristics. Then configure the API implementation to use the mocking service and conduct the performance tests
正解：D
解説：
Correct answer is Create a mocking service that replicates the backend system's production performance characteristics. Then configure the API implementation to use the mocking service and conduct the performance tests
* MUnit is for only Unit and integration testing for APIs and Mule apps. Not for performance Testing, even if it has the ability to Mock the backend.
* Bypassing the backend invocation defeats the whole purpose of performance testing. Hence it is not a valid answer.
* Scaled down performance tests cant be relied upon as performance of API's is not linear against load.
質問 # 50
A retail company is implementing a MuleSoft API to get inventory details from two vendors by Invoking each vendor's online applications. Due to network issues, the invocations to the vendor applications are timing out intermittently, but the requests are successful after re-invoking each What is the most performant way of implementing the API to invoke each vendor application and to retry invocations that generate timeout errors?
- A. Use a Round-Robin scope to invoke each vendor application on a separate route.
Use a Try-Catch scope in each route to retry requests that raise timeout errors. - B. Use a Choice scope to Invoke each vendor application on a separate route.
Place the Choice scope inside an Until-Successful scope to retry requests that raise timeout errors. - C. Use a Scatter-Gather scope to invoke each vendor application on a separate route.
Use an Until-Successful scope in each route to retry requests that raise timeout errors. - D. Use a For-Each scope to invoke the two vendor applications in series, one after the other.
Place the For-Each scope inside an Until-Successful scope to retry requests that raise timeout errors.
正解：D
質問 # 51
Which Exchange asset type represents configuration modules that extend the functionality of an API and enforce capabilities such as security?
- A. Rulesets
- B. RESTAPIs
- C. Connectors
- D. Policies
正解：D
質問 # 52
As part of a growth strategy, a supplier signs a trading agreement with a large customer. The customer sends purchase orders to the supplier according to the ANSI X12 EDI standard, and the supplier creates the orders in its ERP system using the information in the EDI document.
The agreement also requires that the supplier provide a new RESTful API to process request from the customer for current product inventory level from the supplier' s ERP system.
Which two fundamental integration use cases does the supplier need to deliver to provide an end-to-end solution for this business scenario? (Choose two.)
- A. Streaming data ingestion
- B. Sharing data with external partners
- C. Synchronized data transfer
- D. Data mashups
- E. User interface integration
正解：B、C
質問 # 53
An organization is migrating all its Mule applications to Runtime Fabric (RTF). None of the Mule applications use Mule domain projects.
Currently, all the Mule applications have been manually deployed to a server group among several customer hosted Mule runtimes.
Port conflicts between these Mule application deployments are currently managed by the DevOps team who carefully manage Mule application properties files.
When the Mule applications are migrated from the current customer-hosted server group to Runtime Fabric (RTF), fo the Mule applications need to be rewritten and what DevOps port configuration responsibilities change or stay the same?
- A. Yes, the Mule applications Must be rewritten
DevOps Must Still Manage port conflicts. - B. NO, The Mule applications do NOT need to be rewritten
DevOps MUST STILL manage port conflicts - C. Yes, the Mule applications Must be rewritten
DevOps No Longer needs to manage port conflicts between the Mule applications - D. NO, the Mule applications do NO need to be rewritten
DevOps NO LONGER needs to manage port conflicts between the Mule applications.
正解：B
解説：
* Anypoint Runtime Fabric is a container service that automates the deployment and orchestration of your Mule applications and gateways.
* Runtime Fabric runs on customer-managed infrastructure on AWS, Azure, virtual machines (VMs) or bare-metal servers.
* As none of the Mule applications use Mule domain projects. applications are not required to be rewritten. Also when applications are deployed on RTF, by default ingress is allowed only on 8081.
* Hence port conflicts are not required to be managed by DevOps team
質問 # 54
A system administrator needs to determine when permissions were last changed for an Anypoint Platform user.
Which Anypoint Platform component should the administrator use to obtain this information?
- A. Anypoint Monitoring
- B. Audit Logging
- C. Mule Stack Traces
- D. Anypiont Studio
正解：B
質問 # 55
......
試験解答MuleSoft-Integration-Architect-I最新版とテストエンジン：https://jp.fast2test.com/MuleSoft-Integration-Architect-I-premium-file.html
合格させるMuleSoft-Integration-Architect-I試験最新のMuleSoft-Integration-Architect-I試験問題集PDF：https://drive.google.com/open?id=1vcN6aLzkxweWwqcOOWzgmdXUQ9dtSl_m