Which role is primarily responsible for building API implementation as part of a typical MuleSoft integration project?

• A.API Developer
• B.API Designer
• C.Integration Architect
• D.Operations

Comment: *

Name: *

Email: *

Verification: *

An organization has several APIs that accept JSON data over HTTP POST. The APIs are all publicly available and are associated with several mobile applications and web applications. The organization does NOT want to use any authentication or compliance policies for these APIs, but at the same time, is worried that some bad actor could send payloads that could somehow compromise the applications or servers running the API implementations. What out-of-the-box Anypoint Platform policy can address exposure to this threat?

• A.Apply a Header injection and removal policy that detects the malicious data before it is used
• B.Apply an IP blacklist policy to all APIs; the blacklist will Include all bad actors
• C.Shut out bad actors by using HTTPS mutual authentication for all API invocations
• D.Apply a JSON threat protection policy to all APIs to detect potential threat vectors

Comment: *

Name: *

Email: *

Verification: *

An organization has implemented a continuous integration (CI) lifecycle that promotes Mule applications through code, build, and test stages. To standardize the organization's CI journey, a new dependency control approach is being designed to store artifacts that include information such as dependencies, versioning, and build promotions.
To implement these process improvements, the organization will now require developers to maintain all dependencies related to Mule application code in a shared location.
What is the most idiomatic (used for its intended purpose) type of system the organization should use in a shared location to standardize all dependencies related to Mule application code?

• A.API Community Manager
• B.A binary artifact repository
• C.The Anypoint Object Store service at cloudhub.io
• D.A MuleSoft-managed repository at repository.mulesoft.org

Comment: *

Name: *

Email: *

Verification: *

A project team uses RAML specifications to document API functional requirements and deliver API definitions. As per the current legal requirement, all designed API definitions to be augmented with an additional non-functional requirement to protect the services from a high rate of requests according to define service level agreements.
Assuming that the project is following Mulesoft API governance and policies, how should the project team convey the necessary non-functional requirement to stakeholders?

• A.Create various SLA's in API manager for the non functional requirement and publish to exchange
• B.Create proxies in API manager for the non functional requirement and publish to exchange
• C.Update API definitions with the fragment for the appropriate policy and publish to exchange
• D.Add all non functional requirements as comments to RAML specification and publish to exchange

Comment: *

Name: *

Email: *

Verification: *

In one of the critical payment related mule application, transaction is being used . As an enhancement to implementation , scatter gather route is introduced which is also the part of transaction group. Scatter gather route has 4 routes.
What will be the behavior of the Mule application in case of error occurs in 4th route of the scatter-gather router and transaction needs to be rolled back?

• A.Only errored route will be rolled back
• B.All routes will be rolled back
• C.Scatter Gather router cannot be part of transaction

Comment: *

Name: *

Email: *

Verification: *