Salesforce-MuleSoft-Developer-I Exam Dumps - Salesforce MuleSoft Questions and Answers

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

The current version of the RAML specification is 1.0

You can check RAML version in RAML definition by referring to first comment. See highlighted part in below image.

Graphical user interface, text, application, email Description automatically generated

Allowed methods is an optional configuration. If nothing is specified then all HTTP methods are supported.

Rest all are mandatory.

In case of an error , batch job completes in flight steps and stops further processing.

MuleSoft Doc Ref : Handling Errors During Batch Job | MuleSoft Documentation

The default is all processing will stop but we can change it by Max Failed Record field.

General -> Max Failed Records: Mule has three options for handling a record-level error: Finish processing, Continue processing and Continue processing until the batch job accumulates a maximum number of failed records. This behavior can be controlled by Max Failed Records.

The default value is Zero which corresponds to Finish processing.

The value -1, corresponds to Continue processing.

The value +ve integer, corresponds to Continue processing until the batch job accumulates a maximum number of failed records

Correct answer is Nothing needs to be changed in the other APIs or their associated applications

This is the benefit of having separate interface layer. As there are no changes to interface , no changes are required on the API's which consumes this API in context

Correct syntax to use where clause is WHERE city = :city AND state = :state

This question validates knowledge on using dynamic queries in DB select operation.

Configure Dynamic Queries in the Select Operation

When you need to parameterize not only the WHERE clause but also parts of the query itself (for example, queries that compare tables that depend on a condition, or complex queries for which the project table columns need to vary), you can configure dynamic queries.

In the following example, you configure a dynamic query by using a full expression with a string in which the table depends on a variable $(vars.table). Although some of the query text is dynamic ("SELECT * FROM $(vars.table)), the WHERE clause still defines the WHERE condition using input parameters: in this case, WHERE name = :name.

In your Studio flow, select the Select operation.

In the operation configuration screen, set the SQL Query Text field to SELECT * FROM $(vars.table) WHERE name = :name.

Set the Input Parameters field to {'name' : payload}.

The following screenshot shows the configuration in Studio:

Graphical user interface, application Description automatically generated

Figure 3. Dynamic query configuration

In the XML editor, the  configuration looks like this:

• #["SELECT * FROM $(vars.table) WHERE name = :name"]
• #[{'name' : payload}]

You can apply input parameters only to parameters in a WHERE clause. To modify any other part of the query, use the DataWeave interpolation operator.

Mule Ref Doc: Query a Database Examples - Mule 4 | MuleSoft Documentation

The correct answer is To avoid duplicate processing of records in a database.

If a watermark column is provided, the values taken from that column are used to filter the contents of the next poll, so that only rows with a greater watermark value are returned. If an ID column is provided, this component automatically verifies that the same row is not picked twice by concurrent polls.

Mule doc reference : https://docs.mulesoft.com/db-connector/1.8/database-documentation#listener

Option 1 is the correct syntax