MuleSoft Integration Associate Syllabus 2026: All Six Objectives
Most pages show this exam as four sections. The official guide has six, and the credential is now called Integration Foundations. Here is the real outline.
- 40 (+5)Questions
- 70 minTime
- 6Sections
- YesWeights published
- 70%Pass mark
- $75Fee
Table of Contents
The whole paper in one bar
The Salesforce Certified MuleSoft Integration Foundations exam guide is the exam guide Salesforce publishes for Salesforce Certified MuleSoft Integration Foundations, restated so you can see the shape of the paper before you read a word of the detail. The bar below is the entire syllabus: 6 sections, in the order the certifying body lists them.
- §1 Identify the roles, responsibilities and lifecycle of an integration project — 17%
- §2 Recognise and interpret essential integration concepts and terminology — 20%
- §3 Recognise common integration problems, use cases and technical solutions — 17%
- §4 Explain the common technical complexities and patterns in integration development — 18%
- §5 Describe the components and benefits of Anypoint Platform for system integration — 18%
- §6 Describe the components and benefits of Anypoint Platform for API management — 10%
Those percentages are Salesforce’s own, not an estimate. That matters more than it sounds: most pages ranking for this query quote weightings the vendor never published.
The syllabus, section by section
Each block below is one section of the official outline. The bullets are the sub-objectives Salesforce publishes underneath it — the actual scope statement, not a summary of it.
Identify the roles, responsibilities and lifecycle of an integration project
- Why IT integration projects frequently fail
- The IT delivery gap and MuleSoft's approach to closing it
- Characteristics and roles of an API-led delivery model
- Common delivery methodologies for integration projects
- Key DevOps practices and tools for integration
- The design, implement and manage stages of the API lifecycle
- Roles and responsibilities in a MuleSoft project team
Recognise and interpret essential integration concepts and terminology
- IaaS versus PaaS versus SaaS
- Virtualisation, compute and storage; system scalability
- Common networking protocols used in system communication
- Data formats - XML, YAML, JSON
- Core concepts of API and enterprise system security
- HTTP components that enable RESTful web services
- API implementation, proxy, interface, client and invocation
- Classifying REST, SOAP, AsyncAPI and GraphQL APIs
Recognise common integration problems, use cases and technical solutions
- Characteristics of common enterprise systems
- Trade-offs of legacy versus modern integration approaches
- Breaking a business problem into integration use cases
- Classes of integration technology and what each does
- Matching integration technologies to business scenarios
- Deconstructing a solution into its constituent systems
Explain the common technical complexities and patterns in integration development
- Request-reply, one-way, multicast, batch and stream patterns
- Aggregation, orchestration and choreography composition
- API specifications and the design-first approach
- Observability - logs, metrics and tracing
- Designing Mule applications with core connectors
- Cloud, hybrid and on-premises deployment architectures
- Monolithic versus microservices architecture
Describe the components and benefits of Anypoint Platform for system integration
- The primary components of Anypoint Platform
- Popular Anypoint Connectors and their characteristics
- Runtime planes and control planes
- MuleSoft-hosted versus customer-hosted deployment options
- Development tools and languages for integration teams
- Types of reusable asset in Anypoint Exchange
Describe the components and benefits of Anypoint Platform for API management
- Anypoint Platform components for API management
- Full-lifecycle API development and Universal API Management
- Why API-led connectivity beats other integration approaches
Two naming traps. Salesforce renamed this credential to MuleSoft Integration Foundations while leaving the Trailhead URL on the old mulesoftassociate slug, so both names point at the same exam. And Mule-101, the code every listing quotes, is the Pearson VUE registration code — it does not appear in the exam guide at all. Questions align to the Spring 2024 release.
What the weightings really mean
A percentage in an exam guide is a promise about how many questions get drawn from a section, not about how hard those questions are. On a paper of roughly 40 items, Recognise and interpret essential integration concepts and terminology at 20% is worth about 8 questions and Describe the components and benefits of Anypoint Platform for API management at 10% is worth about 4. Missing the whole of the smallest section still leaves you a pass on paper; missing the largest one does not.
The trap is treating that arithmetic as permission to skip. Weightings are the floor of what a section costs you, because the low-weight sections on almost every blueprint are the ones that supply context for questions filed under a different heading. You lose those marks in the heavy section and never find out why.
Reading the verbs in the objectives
The verb at the front of each sub-objective is the part candidates skim and examiners take literally. It sets the depth you are tested at, and it is the difference between recognising a service name and being asked to choose between two that both look right.
| Verb | What a question at that depth looks like |
|---|---|
| Identify / Recognise | Recall-level. Name the component, classify the API style, spot which delivery model is being described. No Mule application to build and no DataWeave to write. |
| Describe / Explain | One layer deeper: what a component is for and which business benefit it delivers. An answer that is technically true but names the wrong benefit is still marked wrong. |
| Distinguish / Compare | The paired-concept verb, and the one that decides this exam. IaaS/PaaS/SaaS, REST/SOAP/AsyncAPI/GraphQL, monolith versus microservices, cloud/hybrid/on-premises, runtime plane versus control plane. |
Nothing on this outline asks you to build anything. It is a foundations exam written for project team members rather than developers, which is exactly why an experienced developer who skips the vocabulary can still fail it.
Study it in this order, not the syllabus order
Exam guides are written to describe a job role, not to teach one. The published order is almost never the order that builds knowledge fastest. This is the sequence that front-loads the material everything else depends on.
| Order | Why here |
|---|---|
| 1. Integration concepts and terminology | 20% and the largest single objective. It is also the vocabulary the other five are written in - service models, protocols, data formats, API styles. |
| 2. Technical complexities and patterns | 18%. Interaction and composition patterns, deployment architectures, observability. Generic integration theory that makes the product tour meaningful. |
| 3. Anypoint Platform for system integration | 18%. Once you know what a runtime and a connector are for, the platform tour becomes a set of answers rather than a list of names. |
| 4. Common integration problems and use cases | 17%. Scenario mapping, and much easier once the patterns from step two are in place. |
| 5. Roles, responsibilities and lifecycle | 17%, and the cheapest to absorb last because by then you already know what each role produces. |
| 6. Anypoint Platform for API management | 10% and smallest, but do not drop it - it is three sub-objectives and they are the most quotable ones on the paper. |
The published order opens with roles and lifecycle. That reads as a gentle warm-up, but it is the section whose answers depend most on knowing what the rest of the exam is about, which is why it belongs near the end of your revision rather than the start of it.
What changed, and how to spot the next change
The credential was renamed from MuleSoft Associate and MuleSoft Integration Associate to MuleSoft Integration Foundations. Objective two now names AsyncAPI and GraphQL alongside REST and SOAP, and objective six is framed around Universal API Management. There is no dated changelog; the only version marker in the guide is that questions align to the Spring 2024 release, which has not been advanced. Salesforce also states there is no required maintenance for this certification at this time.
Two habits keep you from studying a retired outline. First, open the official exam guide and look for its revision date before you buy anything — courses and question banks lag a syllabus change by months, and the cheapest ones never catch up. Second, re-check it the week you book. A revision announced after you started studying is still a revision you sit.
Turn the syllabus into questions
Reading an outline tells you the shape of the paper. Answering questions tells you which sections you would actually lose marks on. Start free, then $5.99 unlocks the full MuleSoft Integration Associate bank.
MuleSoft Integration Associate exam pageFAQ
How many sections does the MuleSoft Integration Associate exam have?
Six, weighted 17%, 20%, 17%, 18%, 18% and 10%. Many third-party pages show a four-section split - that is a rollup that merges two pairs of objectives, not the official outline.
Is MuleSoft Integration Associate the same as MuleSoft Integration Foundations?
Yes. Salesforce renamed the credential to MuleSoft Integration Foundations but left the Trailhead URL on the old mulesoftassociate slug, so both names lead to the same exam. Mule-101 is the Pearson VUE registration code, not a code the exam guide uses.
How much does the MuleSoft Integration Associate exam cost?
US$75 or JPY 10,000 plus applicable taxes for the first attempt, and Salesforce does not charge for retakes on this exam. That makes it one of the cheapest vendor credentials to attempt.
Do I need to know how to build Mule applications?
No. Nothing in the outline asks you to develop, and DataWeave is not an objective. It tests integration vocabulary, patterns and what each Anypoint Platform component is for - which is why developers who skip the vocabulary sometimes fail it.
Sources
Every section title, sub-objective and number on this page comes from the certifying body:
- https://help.salesforce.com/s/articleView?id=005298961&type=1
- https://trailhead.salesforce.com/credentials/mulesoftassociate
- https://www.salesforce.com/trailblazer/credentials/
Checked September 2, 2026. Exam guides are revised without notice — confirm against Salesforce before you build a study plan around this page.