MuleSoft Integration Foundations Study Guide
The Certifyforce MuleSoft Integration Foundations study guide covers the official Salesforce MuleSoft Integration Foundations exam outline in 37 units across all 6 exam sections, one unit per exam-guide topic. The exam itself has 40 scored questions plus 5 unscored, a 70-minute limit and a 70% passing score, and its largest section is Recognize and interpret essential integration concepts and terminology at 20%. Every unit is verified against official Salesforce documentation, cites its sources, and links to the practice questions that test it. Last updated November 2, 2026.
Focused on integration fundamentals and Anypoint Platform: integration project roles and the API lifecycle, essential integration and API terminology, common integration problems and technologies, interaction and composition patterns and deployment architectures, and the Anypoint Platform components for system integration and API management.
37 lessons · 6 exam sections · about 4 h of reading ·
Exam sections
Unlock the full guide
Every lesson's summary, exam expectations, key facts and self-check questions are free to read. The MuleSoft Integration Foundations pack unlocks the self-check answers, core concepts, exam traps and worked scenarios, reading progress and personalized “read next”. Add practice exams for the question bank and unlimited timed practice, or choose the bundle.
Identify the roles, responsibilities, and lifecycle of a integration project
17% of the exam- Technical debt and why integration projects fail~6 minWhy integration projects stall and fail in MuleSoft's analysis: deadline-driven point-to-point shortcuts that become technical debt, siloed teams that rebuild the same integrations, and integration work that crowds out innovation, plus MuleSoft's three steps for reducing the debt.
- The IT delivery gap and application networks~6 minWhat the IT delivery gap is (business demand rising against flat IT capacity), why more resources cannot close it, and how MuleSoft closes it with a production plus consumption model built on an application network of modern, reusable APIs.
- API-led delivery balancing production and consumption~6 minWho produces and who consumes in MuleSoft's API-led delivery model: central IT unlocks systems with System APIs, LoB and central IT compose Process APIs, app developers self-serve to build Experience APIs and apps, with reusable assets created inside projects and consumer feedback steering what is produced next.
- Agile and waterfall delivery for integration projects~5 minHow agile project development (user stories, sprints, continuous integration and delivery) differs from waterfall's all-at-once delivery, the five benefits MuleSoft lists for agile, and why agile alone does not clear an IT backlog.
- DevOps with CI/CD, MUnit and Maven builds~6 minThe four DevOps practices MuleSoft names, how a CI/CD pipeline for Mule applications splits work across version control, Maven, MUnit and release tools, and how the Mule Maven plugin and MUnit Maven plugin build, test and deploy an app.
- Design, implement and manage API lifecycle stages~6 minThe three stages of MuleSoft's product-centric API lifecycle and the steps inside each (design, simulate, feedback and validate; build and test; secure, deploy, monitor, troubleshoot and manage), traced through MuleSoft's build-an-API tutorial.
- Integration project team roles and the C4E~7 minHow MuleSoft builds a DevOps team structure in four steps, the six tiger-team roles and what each one owns, and why a Center for Enablement (C4E) replaces the bottlenecked Integration Competency Center with a cross-functional team that drives asset reuse.
Recognize and interpret essential integration concepts and terminology
20% of the exam- IaaS, PaaS and SaaS service models~6 minHow MuleSoft stacks the three cloud service models, with SaaS on top, PaaS in the middle and IaaS at the bottom, what each one delivers and leaves to the customer, and why CloudHub is classed as an iPaaS, a PaaS subcategory for integration.
- Virtualization, containers and system scalability~7 minThe compute and storage building blocks behind Mule deployments (virtual machines, bare-metal servers, containers on Kubernetes, replica disk and external object stores) and the principles of vertical and horizontal scaling, high availability clusters and load balancing.
- Networking protocols from HTTPS to SFTP~6 minClassifies the protocols Mule applications use (HTTP and HTTPS for requests, FTP, FTPS and SFTP for files, TCP, UDP and WebSockets for sockets, JMS and VM for queues), shows where TLS fits, and explains why load balancers help socket traffic but not file polling.
- JSON, XML and YAML data formats~5 minHow JSON, XML and YAML structure data (objects and arrays, repeated elements with attributes and namespaces, indented mappings and sequences), which ones DataWeave reads and writes in transformations, and why YAML and .properties files hold Mule configuration properties.
- Authentication, authorization and encryption for APIs~7 minMuleSoft's three principles of API security (identity and access management, content integrity and confidentiality, reliability and availability), how tokens, OAuth 2.0, signatures and encryption fit into them, and which part of Anypoint Platform secures users, APIs and threats.
- HTTP methods, status codes and REST constraints~6 minHow a RESTful API uses HTTP: methods mapped to create, read, update and delete, URI parameters, query parameters and headers, the status codes that report success or failure, and the six REST constraints such as statelessness and cacheability.
- API implementation, proxy, interface, client and invocation~6 minThe Anypoint Platform glossary terms for the parts of an API: the interface or specification (the contract), the implementation that realizes it, the instance, the proxy that applies policies in front of a backend, and the client application that invokes the API with its own credentials.
- REST, SOAP, AsyncAPI and GraphQL API styles~6 minHow to classify an API from its clues: REST resources and HTTP methods, SOAP's WSDL and XML envelope, GraphQL's single endpoint with client-chosen fields, and event-driven APIs described with AsyncAPI events, channels and transports, plus when asynchronous beats synchronous.
Recognize common integration problems, use cases, and technical solutions
17% of the exam- ERP, CRM and MDM enterprise systems~6 minHow to tell the common enterprise system classes apart: ERP for core back-office processes on one database, CRM for customer interactions, MDM for one governed reference point for master data, and the data warehouse for reporting, plus why each still needs integration.
- Point-to-point, ESB and SOA integration tradeoffs~6 minThe tradeoffs MuleSoft describes as integration moved from point-to-point links and ETL tools through hub-and-spoke brokers to the ESB, and how SOA differs from microservices and API-led connectivity.
- Migration, broadcast, sync, correlation and aggregation use cases~6 minMuleSoft's five data integration patterns (migration, broadcast, bi-directional sync, correlation and aggregation), the questions that identify each one, and how to break a business problem into several of them.
- ESB, iPaaS and API management technology classes~6 minWhat each class of integration technology is for: the ESB as a bus architecture with routing, transformation and protocol services, iPaaS as cloud-native integration, full lifecycle API management for governing APIs, and message queuing for asynchronous exchange.
- Choosing ETL, iPaaS, events or API gateways~5 minHow to match a business scenario to the right integration technology: ETL for batch warehouse loads, a hybrid-capable iPaaS for cloud-to-on-premises connectivity, event-driven processing for act-now needs, and API management with a gateway for secured, throttled, discoverable APIs.
- Systems, connectors and apps in an integration solution~5 minHow to break an integration solution into its constituents: the systems and the APIs they expose, the connectors (endpoint-based or operation-based) that reach them, the integration application that routes and transforms data between them, and the API-led layer each API belongs to.
Explain the common technical complexities and patterns in integration development
18% of the exam- Request-reply, one-way, multicast, batch and stream patterns~6 minHow the five interaction patterns differ: blocking request-reply, one-way messaging through a queue, multicast through an Anypoint MQ message exchange, Mule batch jobs for larger-than-memory record sets, and Mule 4 repeatable streams for large payloads.
- Aggregation, orchestration and choreography composition patterns~6 minHow the three composition patterns place control: aggregation fans one request out in parallel and combines the results with Scatter-Gather, orchestration puts the logic in a central controller, and choreography lets each service know its own part with no coordinator.
- API specifications, mocking and design-first development~5 minWhat an API specification is and why designing it first pays off: the languages API Designer supports, the mocking service that lets consumers try an API before code exists, and sharing one contract through Exchange, Studio and API Manager.
- Logs, metrics and tracing for observability~6 minHow logs, metrics and distributed traces answer different operational questions, what Anypoint Monitoring offers for each (with its tier and deployment limits), and how synthetic testing and real-user monitoring complement each other.
- HTTP, Database, File connectors and core components~6 minHow a Mule flow is assembled from a source, connector operations and core components: HTTP Listener versus HTTP Request, Database Connector over JDBC, File Connector on a local file system, the Scheduler and the For Each scope.
- Cloud, hybrid and on-premises deployment architectures~6 minHow cloud, hybrid and on-premises architectures differ in where management and runtimes run, who supplies and patches the infrastructure, and where data stays, and why hybrid is the usual middle ground.
- Monolithic versus microservices architecture tradeoffs~6 minWhat makes an application a monolith, what microservices gain by splitting it into independently deployed services behind business APIs, and the complexity, discovery and DevOps costs that come with that flexibility.
Describe the components and benefits of Anypoint Platform for system integration
18% of the exam- Anypoint Platform integration components and their roles~7 minThe Anypoint Platform component map for integration: Design Center's API Designer, Exchange, Mule runtime engine, Runtime Manager, Anypoint MQ, Partner Manager and Anypoint Monitoring, and how to match a project task to the component that does it.
- Anypoint Connector support levels and categories~5 minHow Anypoint Connectors are grouped by what they connect to (software applications, databases, protocols), the three support categories (Select, Premium, MuleSoft Certified), the roles a connector plays in a flow, and where to find more connectors.
- Control plane and runtime plane responsibilities~5 minWhat the Anypoint Platform control plane (management, identity, design-time metadata) and runtime plane (Mule runtime engine and services where apps run) each hold, how clouds such as US Cloud and EU Cloud set data residency, and how the Runtime Manager agent links customer-hosted runtimes to the control plane.
- CloudHub, Runtime Fabric and hybrid deployment options~6 minThe runtime plane hosting options: MuleSoft-hosted CloudHub and CloudHub 2.0, customer-hosted Runtime Fabric on your own Kubernetes cluster, hybrid standalone runtimes managed from Runtime Manager, and fully disconnected on-premises runtimes, with who manages what and how CloudHub reaches private systems.
- Studio, Code Builder, CLI and DataWeave tooling~5 minThe developer and DevOps toolset: Anypoint Studio (Eclipse-based IDE), Anypoint Code Builder (VS Code), Anypoint CLI for scripted automation, MUnit for tests, and the languages behind them: Mule configuration XML, DataWeave and RAML.
- Anypoint Exchange asset types and sharing~6 minWhat Anypoint Exchange catalogs (APIs, spec fragments, connectors, templates, examples, DataWeave libraries, policies, rulesets and more), how to tell similar asset types apart, and who can see an asset: your organization, your business group, everyone (Provided by MuleSoft) or an Exchange public portal.
Describe the components and benefits of Anypoint Platform for API management
10% of the exam- API Manager, API Governance and API Experience Hub~6 minWhat API Manager, the embedded Mule Gateway, API Governance and API Experience Hub each do for a managed API: contracts, policies, alerts and API groups; rulesets and conformance; and developer portals.
- Universal API Management across the full API lifecycle~6 minWhy API sprawl calls for Universal API Management, how Anypoint products map to the design and build, discover, govern, manage and secure, and engage stages, and how API Catalog CLI and Omni Gateway reach APIs built anywhere.
- Reuse and change isolation with API-led connectivity~5 minWhy API-led connectivity beats point-to-point integration: reuse that speeds later projects and cuts costs, System APIs that isolate backend change, and an application network that bends instead of breaking.
Common questions about the MuleSoft Integration Foundations study guide
Is the MuleSoft Integration Foundations study guide free?
Partly. Every unit's summary and its "What the exam expects", "Key facts" and "Check yourself" sections are free to read without an account. The "Core concepts", "Exam traps" and "Worked scenario" sections, reading progress and unlimited timed mock exams come with the MuleSoft Integration Foundations pack (USD $19).
How current is the MuleSoft Integration Foundations study guide?
It is written to the current official Salesforce MuleSoft Integration Foundations exam outline, and each unit is checked against Salesforce documentation before it is published. The most recent update was November 2, 2026, and every unit shows its own last-updated date.
How does the study guide map to the official MuleSoft Integration Foundations exam guide?
There is one unit per topic in the official exam guide, grouped under its 6 weighted sections: Identify the roles, responsibilities, and lifecycle of a integration project (17%), Recognize and interpret essential integration concepts and terminology (20%), Recognize common integration problems, use cases, and technical solutions (17%), Explain the common technical complexities and patterns in integration development (18%), Describe the components and benefits of Anypoint Platform for system integration (18%), Describe the components and benefits of Anypoint Platform for API management (10%). Each unit quotes the exam objective it covers word for word.
How do the practice questions link to the study guide?
Each unit lists the reviewed practice questions that test it (151 questions are linked across the guide), so you can read a topic and practice it in one click. After a practice exam, every missed question links back to the unit that teaches it.