MuleSoft Certified Developer – Integration and API

Associate (Mule 3) Certification Exam

Summary
A MuleSoft Certified Developer – Integration and API Associate (Mule 3) should be able to successfully
work on basic Mule 3 projects with guidance and supervision. The MCD – Integration and API
Associate (Mule 3) exam validates that a developer has the required knowledge and skills to design,
build, test, debug, deploy, and manage basic APIs and integrations: moving from Anypoint Platform to
Anypoint Studio and back. Certified candidates should be able to:

• Use MuleSoft-hosted Anypoint Platform to take a basic API through all the steps of its lifecycle:
design, build, deploy, manage, and govern.
• Use Anypoint Studio to build, test, and debug basic integrations and API implementations.
• Connect to a range of resources — including databases, files, web services, SaaS applications,
and JMS queues.
• Perform basic data transformations using DataWeave.
• Control message flow and handle errors.
• Process batch records.

Format
• Format: Multiple-choice, closed book
• Length: 60 questions
• Duration: 120 minutes (2 hours)
• Pass score: 70%
• Language: English
You can take the exam a maximum of 5 times, with a 24-hour wait between each attempt.

Cost
You can purchase the exam with one of the following. Each includes one free retake.

• $250
• 1 Flexible Training Credit (FTC)
Additional retakes (i.e. attempts 3 to 5) are $125 or 0.5 FTC off and do not come with a free retake.

Two free exam attempts are also included with the purchase of the instructor-led Anypoint Platform
Development: Fundamentals (Mule 3).
Validity
The certification expires two years from the date you pass the exam.

Preparation
You can best prepare for the exam by taking the instructor-led Anypoint Platform Development:
Fundamentals (Mule 3) course and completing the accompanying Do-It-Yourself (DIY) exercises.
Candidates should be familiar with all of the content in the course and be able to apply the
concepts in actual projects.

The following resources are available to help you prepare:

• Instructor-led training: Anypoint Platform Development: Fundamentals (Mule 3)

o Recommended as the most effective and efficient method of preparation
o 5-day class
o Private, public, onsite, and online available
o Includes two free attempts for this exam
• Self-study training: Anypoint Platform Development: Fundamentals (Mule 3)
o 30+ hours of video-based training with 60+ exercises to teach you the basics
o All content available instantly for you to complete at your own pace
o Supported by the peer-to-peer MuleSoft training forum
o Does not include any free attempts for this exam
• Self-assessment quiz
o 5+ multiple-choice questions for each course module
o Identifies strengths and weaknesses
• Do-it-yourself exercises
o 10+ DIY exercises to get experience with and apply the knowledge gained in class
o Starting code and solutions provided
o Can be completed in any order
Topics
The exam validates that the candidate can perform the following tasks.

Note: DEV: FUN3 is the acronym for the Anypoint Platform Development: Fundamentals (Mule 3).
DEV: DIY3 is the acronym for the Development Fundamentals (Mule 3) Self-Assessment Quiz & DIY
Exercises materials.

Explaining application network basics Resources

• Explain MuleSoft’s proposal for closing the IT delivery gap. • DEV: FUN3 Module 1
• Describe the role and characteristics of the “modern API.” • DEV: FUN3 Module 2
• Describe the purpose and roles of a Center for Enablement (C4E).
• Define and describe the benefits of API-led connectivity and
application networks.
• Define and correctly use the terms API, API implementation, API
interface, API consumer, and API invocation.
• Describe the basics of the HTTP protocol and the characteristics of
requests and responses.
• Describe the capabilities and high-level components of Anypoint
Platform for the API lifecycle.

Designing and consuming APIs

• Describe the lifecycle of the “modern API.” • DEV: FUN3 Module 3

• Use RAML to define API resources, nested resources, and methods. • DEV: DIY3 Exercise 3-1
and 4-1
• Identify when and how to define query parameters vs URI
parameters.
• Use RAML to define API parameters, requests, and responses.
• Use RAML to define reusable data types and format-independent
examples.
• Read a RAML spec and formulate RESTful requests with query
parameters and/or headers as appropriate.

Accessing and modifying Mule messages

• Describe the Mule message data structure. • DEV: FUN3 Module 6

• Use transformers to set message payloads, message properties, and • DEV: DIY3 Exercise 6-1
flow variables.
• Write MEL expressions to access and modify message payloads,
message properties, and flow variables.
• Enrich Mule messages using the Message Enricher.
Structuring Mule applications

• Parameterize an application using property placeholders. • DEV: FUN3 Module 7

• Define and reuse global configurations in an application. • DEV: DIY3 Exercise 7-1
and 7-2
• Break an application into multiple flows using private flows, subflows,
and the Flow Reference component.
• Specify what data (payload, message properties, flow variables) is
persisted between flows when a Flow Reference is used.
• Specify what data (payload, message properties, flow variables) is
persisted between flows when a Mule message crosses a transport
boundary.
• Specify what data (payload, message properties, flow variables)
exists in a flow before and after a call in the middle of a flow to an
external resource.

Building API implementation interfaces

• Manually create a RESTful interface for a Mule application. • DEV: FUN3 Module 4
• Describe the features and benefits of APIkit. • DEV: DIY3 Exercise 4-1
• Use APIkit to create implementation flows from a RAML file.
• Describe how requests are routed through flows generated by APIkit.

Routing messages

• Use the Choice router to route messages based on conditional logic. • DEV: FUN3 Module 10
• Use the Scatter-Gather router to multicast messages. • DEV: DIY3 Exercise 10-
1 and 10-2
• Use Filters to filter Mule messages.
• Validate data using the Validation module.

Handling errors

• Describe the default exception strategy in a Mule application. • DEV: FUN3 Module 9
• Define a custom global default exception strategy for an application • DEV: DIY3 Exercise 9-1
and identify in what situations it will be used. and 9-2
• Define exception strategies for flows.
• Combine multiple catch exception strategies in a choice exception
strategy.
Transforming data with DataWeave

• Write DataWeave scripts to convert JSON, XML, and Java data • DEV: FUN3 Module 11
structures to different data structures and data types. • DEV: DIY3 Exercise 11-
• Use DataWeave operators. 1
• Define and use custom data types.
• Apply correct DataWeave syntax to coerce data types.
• Apply correct DataWeave syntax to format strings, numbers, and
dates.
• Call Mule flows from a DataWeave script.
• Call global MEL functions from a DataWeave script.

Using Connectors

• Retrieve data from a Database using the Database connector. • DEV: FUN3 Module 4
• Retrieve data from a REST service using HTTP Request. • DEV: FUN3 Module 8
• Use a Web Service Consumer connector to consume SOAP web • DEV: FUN3 Module 12
services.
• DEV: DIY3 Exercise 4-1,
• Use the Transform Message component to pass arguments to a 8-1, 12-1, and 12-2
SOAP web service.
• List, read, and write local files using the File connector.
• List, read, and write remote files using the FTP connector.
• Use the JMS connector to publish and listen for JMS messages.

Processing records

• List and compare and contrast the methods for processing individual • DEV: FUN3 Module 12
records in a collection.
• DEV: FUN3 Module 13
• Explain how Mule messages are processed by the Foreach scope . • DEV: DIY3 Exercise 13-
• Use the Foreach scope to process records. 1
• Explain how Mule messages are processed in a Batch job.
• Use a Batch element with Batch Steps, Batch Filters, and a Batch
Commit to process records.
• Use the Poll component to trigger a flow.
• Describe the features, benefits, and process to use watermarking.
• Configure watermarks in the Poll scope.
• Persist data between flow executions using the Object Store.
Debugging and troubleshooting Mule applications

• Use breakpoints to inspect a Mule message during runtime. • DEV: FUN3 Module 6
• Install missing dependencies and drivers to a Mule project. • DEV: FUN3 all WTs
• Read and decipher Mule log error messages. • DEV: DIY3 Exercise 6-1
• DEV: DIY3 all exercises

Deploying and managing APIs and integrations

• Package Mule applications for deployment. • DEV: FUN3 Module 5

• Deploy applications to CloudHub. • DEV: DIY3 Exercise 5-1
and 5-2
• Use CloudHub properties to ensure deployment success.
• Configuring API
• Create and deploy API proxies.
Autodiscovery in a Mule
• Connect an API implementation to API Manager using 3 Application
autodiscovery.
• Use policies, including client ID enforcement, to secure an API.
• Create SLA tiers and apply SLA based policies.

More information
For more information, visit http://help.learn.mulesoft.com.