- Email support@dumps4free.com
A retailer is designing a data exchange interface to be used by its suppliers. The interface must support secure communication over the public internet. The interface must also work with a wide variety of programming languages and IT systems used by suppliers.
What are suitable interface technologies for this data exchange that are secure, cross-platform, and internet friendly, assuming that Anypoint Connectors exist for these interface technologies?
A. EDJFACT XML over SFTP JSON/REST over HTTPS
B. SOAP over HTTPS HOP over TLS gRPC over HTTPS
C. XML over ActiveMQ XML over SFTP XML/REST over HTTPS
D. CSV over FTP YAML over TLS JSON over HTTPS
Explanation
* As per definition of API by Mulesoft , it is Application Programming Interface using HTTP-based protocols. Non-HTTP-based programmatic interfaces are not APIs.
* HTTP-based programmatic interfaces are APIs even if they don’t use REST or JSON. Hence implementation based on Java RMI, CORBA/IIOP, raw TCP/IP interfaces are not API's as they are not using HTTP.
* One more thing to note is FTP was not built to be secure. It is generally considered to be an insecure protocol because it relies on clear-text usernames and passwords for authentication and does not use encryption.
* Data sent via FTP is vulnerable to sniffing, spoofing, and brute force attacks, among other basic attack methods.
Considering the above points only correct option is
-XML over ActiveMQ
- XML over SFTP
- XML/REST over HTTPS
An organization has just developed a Mule application that implements a REST API. The mule application will be deployed to a cluster of customer hosted Mule runtimes. What additional infrastructure component must the customer provide in order to distribute inbound API requests across the Mule runtimes of the cluster?
A. A message broker
B. An HTTP Load Balancer
C. A database
D. An Object Store
Explanation
Correct answer is An HTTP Load Balancer.
Key thing to note here is that we are deploying application to customer hosted Mule runtime. This means we will need load balancer to route the requests to different instances of the cluster.
Rest all options are distractors and their requirement depends on project use case.
What limits if a particular Anypoint Platform user can discover an asset in Anypoint Exchange?
A. Design Center and RAML were both used to create the asset
B. The existence of a public Anypoint Exchange portal to which the asset has been published
C. The type of the asset in Anypoint Exchange
D. The business groups to which the user belongs
Explanation
* "The existence of a public Anypoint Exchange portal to which the asset has been published" - question does not mention anything about the public portal. Beside the public portal is open to the internet, to anyone. * If you cannot find an asset in the current business group scopes, search in other scopes. In the left navigation bar click All assets (assets provided by MuleSoft and your own master organization), Provided by MuleSoft, or a business group scope. User belonging to one Business Group can see assets related to his group only Reference:
https://docs.mulesoft.com/exchange/to-find-info
https://docs.mulesoft.com/exchange/asset-details
Correct answer is The business groups to which the user belongs
A mule application is being designed to perform product orchestration. The Mule application needs to join together the responses from an inventory API and a Product Sales History API with the least latency. To minimize the overall latency. What is the most idiomatic (used for its intended purpose) design to call each API request in the Mule application?
A. Call each API request in a separate lookup call from Dataweave reduce operator
B. Call each API request in a separate route of a Scatter-Gather
C. Call each API request in a separate route of a Parallel For Each scope
D. Call each API request in a separate Async scope
Explanation:
Scatter-Gather sends a request message to multiple targets concurrently. It collects the responses from all routes, and aggregates them into a single message.
Reference: [Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept, ]
An organization is building out a test suite for their application using MUnit. The Integration Architect has recommended using Test Recorder in Anypoint Studio to record the processing flows and then configure unit tests based on the captured events. What Is a core consideration that must be kept In mind while using Test Recorder?
A. The Recorder supports loops where the structure of the data being tested changes inside the Iteration
B. Mocking values resulting from parallel processes are possible and will not affect theexecution of the processors that follow in the test
C. The Recorder supports mocking a message before or inside a Foreach processor
D. Tests for flows cannot be created if Mule errors are raised Inside the flows, even if the errors are handled by On-Error Continue error handlers
Explanation:
MUnit and Test Recorder:
Core Consideration:
Error Handling in MUnit:
References:
MuleSoft Documentation on MUnit: MUnit Documentation
MuleSoft Blog on MUnit Test Recorder: MUnit Test Recorder
| Page 13 out of 54 Pages |
| Previous |