Salesforce MuleSoft-Integration-Architect-I Test Dumps

B.   Add encrypted versions of the sensitive properties as global configuration properties in the Mule application

D.   Create a parent POM of all the required dependencies and reference each in each application's POM.xml file

C.   Application C uses the Object Store connector to access a persistent object Application P accesses the persistent object store via the Object Store REST API

Answer DescriptionExplanation: Explanation Correct answer is Application A accesses the persistent object store via the Object Store REST API Application B uses the Object Store connector to access a persistent object * Object Store v2 lets CloudHub applications store data and states across batch processes, Mule components and applications, from within an application or by using the Object Store REST API. * On-premise Mule applications cannot use Object Store v2. * You can select Object Store v2 as the implementation for Mule 3 and Mule 4 in CloudHub by checking the Object Store V2 checkbox in Runtime Manager at deployment time. * CloudHub Mule applications can use Object Store connector to write to the object store * The only way on- premises Mule applications can access Object Store v2 is via the Object Store REST API. * 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.

D.   Apply a JSON threat protection policy to all APIs to detect potential threat vectors

Answer DescriptionExplanation: Explanation We need to note few things about the scenario which will help us in reaching the correct solution. Point 1 : The APIs are all publicly available and are associated with several mobile applications and web applications. This means Apply an IP blacklist policy is not viable option. as blacklisting IPs is limited to partial web traffic. It can't be useful for traffic from mobile application
Point 2 : The organization does NOT want to use any authentication or compliance policies for these APIs. This means we can not apply HTTPS mutual authentication scheme.
Header injection or removal will not help the purpose.
By its nature, JSON is vulnerable to JavaScript injection. When you parse the JSON object, the malicious code inflicts its damages. An inordinate increase in the size and depth of the JSON payload can indicate injection. Applying the JSON threat protection policy can limit the size of your JSON payload and thwart recursive additions to the JSON hierarchy.
Hence correct answer is Apply a JSON threat protection policy to all APIs to detect potential threat vectors

B.   Automated testing with MUnit

Answer DescriptionExplanation: To improve delivery quality, a MuleSoft integration team should adopt automated testing with MUnit. MUnit is MuleSoft's testing framework that allows developers to create, design, and run unit and integration tests on their Mule applications. Automated testing with MUnit ensures that each part of the Mule application is tested for correctness and performance, catching issues early in the development cycle. This practice leads to higher quality code, reduced defects, and more reliable integrations.
Other practices mentioned, such as continuous design with API Designer and passive monitoring with Anypoint Monitoring, are important but do not directly address the need for rigorous and automated testing to ensure quality.

B.   Increased developer productivity through sell-service of API assets

Answer DescriptionExplanation: According to MuleSoft, a significant business benefit associated with an API-led connectivity approach using Anypoint Platform is increased developer productivity through self-service of API assets. API-led connectivity promotes the creation of reusable APIs that can be easily discovered and consumed by developers across the organization. This self- service model reduces dependencies, accelerates development, and fosters innovation by enabling teams to quickly build and integrate applications using existing APIs without waiting for central IT to provide access.

A.   SLAs and non-functional requirements to access the backend systems

Answer DescriptionExplanation: SLAs and non-functional requirements to access the backend systems. Only this option actually speaks to design parameters and reqs. * Below two are technical implementations and not the part of design: - Snapshots of the Mule application’s flows, including their error handling - The credentials to access the backend systems and contact details for the administrator of each system * List of consumers is not relevant to the design

B.   For Each scope in the parent flow
On Error Continue error handler in the child flow

Answer DescriptionExplanation: Explanation Correct answer is For Each scope in the parent flow On Error Continue error handler in the child flow. You can extract below set of requirements from the question a) Records should be sent to downstream system in the same order that it was received in the array b) Any validation or communication failures should not prevent further processing of the remaining records First requirement can be met using For Each scope in the parent flow and second requirement can be met using On Error Continue scope in child flow so that error will be suppressed.