Salesforce Updated Salesforce-MuleSoft-Developer-I Exam Questions and Answers by winston

*RAML file contains lot of information that could be considered as "not API-describing". Sort of "economy-class" members.

Equally important, but not necessarily part of the main RAML file.

* Through !includes, RAML allows us to build file-distributed API definitions, which is not only useful to encourage code reuse but also improves readability.

* We can create RAML fragments with such code and then include them in main RAML project using !include like:

types:

Book: !include bookDataType.raml and

examples:

input: !include bookExample.raml

* Additionally for

----------------------------------------------------------------------------------------------------------------------------------------

Correct Answer: D

Choice router finds the FIRST true condition, then distribute the event to the ONE matched route.

MuleSoft Doc Ref: https://docs.mulesoft.com/mule-runtime/4.1/choice-router-concept

The Choice router dynamically routes messages through a flow according to a set of DataWeave expressions that evaluate message content. Each expression is associated with a different routing option. The effect is to add conditional processing to a flow, similar to an if/then/else code block in most programming languages.

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggersthat route’s execution and the others are not checked. If none of the expressions are true, then the default route executes.

Diagram Description automatically generated

Correct answer is Select only Attach Project Sources only

You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace.

Deselect the Include project modules and dependencies option.

This option skips bundling the actual modules and external dependencies required to run the Mule application in a Mule runtime engine, creating a lightweight JAR file package that does not include any dependencies specified in the Mule application’s pom.xml file.

The generated JAR file is not a functional deployable archive and cannot be deployed to a Mule runtime engine, but instead offers a way to archive only the source files that make up the Mule application. This is the same as using the -lightWeightPackage flag when packaging using the Mule Maven Plugin and is useful if you want to distribute your project to other Studio installations because it only keeps a reference to all its dependencies. When you import a lightweight package into Studio, all your dependencies are automatically downloaded

MuleSoft Doc Ref : https://docs.mulesoft.com/studio/7.8/import-export-packages

API portal are created by API Exchange and cannot be created by Design Center