Free Preparation Discussions
MENU
Salesforce MuleSoft Developer I Exam Questions
- Salesforce Developer Certifications
- Salesforce MuleSoft Developer I Certifications
- Topic 1: Creating Application Networks: The topic of creating Application Networks encompasses understanding MuleSoft’s proposal for closing the IT delivery gap and describing the role and characteristics of the modern API. It also includes the purpose and roles of a Center for Enablement (C4E), and the benefits of API-led.
- Topic 2: Designing APIs: Designing APIs involves describing the lifecycle of the modern API and using RAML to define various aspects of an API. It includes identifying when to use query parameters vs URI parameters, and defining API parameters.
- Topic 3: Accessing and Modifying Mule Events: It describes the Mule event data structure. Moreover, the topic focuses on usage of transformers and enriching Mule events.
- Topic 4: Structuring Mule Applications: Structuring Mule applications covers parameterizing an application and defining and reusing global configurations. It includes breaking an application into multiple flows using private flows, subflows, and the Flow Reference component.
- Topic 5: Building API Implementation Interfaces: This topic involves manually creating a RESTful interface for a Mule application and generating a REST Connector from a RAML specification. It also includes describing the features and benefits of APIkit.
- Topic 6: Using Connectors: It focuses on retrieving data from REST services using HTTP Request or REST Connector. Moreover, the topic covers using a Web Service Consumer connector for SOAP web services and the Transform Message component.
- Topic 7: Processing Records: Processing records includes methods for processing individual records in a collection and explaining how Mule events are processed by the For Each scope. It also involves using the Batch Job with Batch Steps and a Batch Aggregator.
- Topic 8: Transforming Data with DataWeave: It involves writing DataWeave scripts and using DataWeave functions. This topic also includes defining and using DataWeave variables, functions, and modules, and applying correct syntax.
- Topic 9: Routing Events: It focuses on using the Choice router for conditional logic and the Scatter-Gather router to multicast events. This topic also involves validating data by using the Validation module.
- Topic 10: Handling Errors: Handling errors includes describing default error handling in Mule applications and defining custom global default error handlers. It involves comparing On Error Continue and On Error Propagate scopes, creating error handlers for a flow, using the Try scope, and mapping errors to custom application errors.
- Topic 11: Debugging and Troubleshooting Mule Applications: Using breakpoints to inspect a Mule event during runtime, installing missing Maven dependencies, and reading and deciphering Mule log error messages are sub-topics of this topic.
- Topic 12: Deploying and Managing APIs and Integrations: It includes packaging Mule applications for deployment and deploying them to CloudHub. This topic also involves using CloudHub properties, creating and deploying API proxies, connecting an API implementation to API Manager, and applying policies to secure an API.
Free Salesforce Salesforce MuleSoft Developer I Exam Actual Questions
Note: Premium Questions for Salesforce MuleSoft Developer I were last updated On Mar. 30, 2025 (see below)
Refer to the exhibits.
The Validation component in the Try scope throws an error.
What response message is returned to a client request to the main flow's HTTP Listener?
The Validation component in the Try scope throws an error. What response message is returned to a client request to the main flow's HTTP Listener?
Note that private flow has error scope defined as On Error Continue . So when error occurs in private flow , it is handled by this On Error Continue scope which sends success response back to main flow and does not throw back an error. So main continues normally and payload is set to Success - main flow.
Hence correct answer isSuccess - main flow
1) HTTP listener received request
2) The Flow Reference calls the child flow
3) The Is Number validator creates an Error Object because the payload isn't an integer. Child Flow execution stops
#[error.description] = ''payload is not a valid INTEGER value''
#[error.errorType] = VALIDATION:INVALID_NUMBER
4) The On Error Continue handles the errorThe payload is set to ''Error -- Sub Flow''
5) ''Error -- Sub Flow'' is returned to the main flow as if the child flow was a success. The Set Payload is executed. The payload is reset to ''Success -- Finished Main Flow''
6) ''Success -- Main Flow'' is returned to the requestor in the body of the HTTP request. HTTP Status Code: 200
As you can see, in the above example, because the error was caught by an On Error Continue scope in the child flow (RED in, GREEN out) when the Mule Message returns to the parent flow, the parent flow knows none-the-different that there was a failure because the on error continue returns a 200 success message. Note that because, to the mainFlow, the childFlow appeared to succeed, the processing of mainFlow resumed after the flow reference.
A company has defined two RAML fragments, Book Data Type and Book Example to be used in APIs.
What would be valid RAML to use these fragments ?
* 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
Refer to the exhibit.
What is the correct syntax to add a customer ID as a URI parameter in an HTTP Listener's path attribute?
Refer to the exhibit.
What is the correct way to create a user?
A)
B)
C)
D)
Where are values of query parameters stored in the Mule event by the HTTP Listener?
Correct answer isAttributes.
Query parameters , URI parameters and headers are some of examples which are part of attributes.
Bottom of Form
Top of Form
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Aileen
14 days agoAlishia
18 days agoDustin
27 days agoJoesph
1 months agoHobert
2 months agoArleen
2 months agoDelisa
2 months agoLashaunda
2 months agoTheron
3 months agoElsa
3 months agoFelicia
3 months agoMargret
3 months agoBerry
4 months agoLarue
4 months agoWai
4 months agoKatlyn
4 months agoWhitley
4 months agoAlline
5 months agoJolene
5 months agoElinore
5 months agoEvette
5 months agoLeatha
5 months agoRene
5 months agoLindsey
6 months agoAnnmarie
6 months agoGayla
6 months agoAron
6 months agoErick
6 months agoYuki
7 months agoJeannetta
7 months agoHeike
7 months agoMollie
8 months agoBenton
9 months agoDelmy
9 months agoBette
10 months agoLang
10 months agoMarget
10 months agoCeola
10 months agoDelisa
10 months agoParis
10 months ago