The Short Answer
The Salesforce Certified MuleSoft Platform Integration Architect exam has 60 multiple-choice questions plus up to five unscored ones, 120 minutes, a 70% passing score, a US$400 registration fee, a US$200 retake fee and no prerequisite. The questions align to the Spring '24 release. All of this was checked in November 2026 against the official exam guide.
Think of it as the exam for the person who designs the integration solution and then has to keep it running. Runtime topology, Mule application design, persistence, reliability, performance, security and DevOps make up most of the outline. The two biggest sections, runtime plane architecture and designing and developing Mule applications, are 15% each.
Exam Details at a Glance
Everything in this table is from the exam guide.
| Detail | MuleSoft Platform Integration Architect |
|---|---|
| Questions | 60 multiple-choice, plus up to 5 unscored |
| Time | 120 minutes (the time allows for the unscored questions) |
| Passing score | 70% |
| Registration fee | US$400 (JPY 60,000), plus applicable taxes |
| Retake fee | US$200 (JPY 30,000), plus applicable taxes |
| Prerequisite | None |
| Alignment | Spring '24 release |
| Delivery | Proctored, at a testing center or online |
| References | None allowed during the exam |
| Maintenance | None required at this time |
The guide recommends the MuleSoft Developer certification before this one but says it is not required. If you've already passed it, you have the vocabulary. If you haven't, expect to learn Mule 4 basics along the way, because the questions assume you've built and deployed non-trivial Mule applications.
How It Differs From MuleSoft Platform Architect
Both exams sit at the top of the MuleSoft track, and they're easy to mix up. They test different jobs.
The Platform Integration Architect guide describes someone who drives an organization's Anypoint Platform implementation and is responsible for technical quality, governance and operationalization of integration solutions. The candidate creates high-level designs, advises implementation teams on which Mule components and patterns to use, and chooses deployment options. Typical roles listed are solution architects, technical architects and senior developers.
The MuleSoft Platform Architect guide covers the other side: strategy for the platform and the application network as a whole. That exam is about who owns which API, how APIs are governed and how a Center for Enablement is organized. This one is about what happens inside and underneath a single integration solution: how Mule applications run, how they persist state, survive failures and get delivered.
A quick test: if the question is "how should this organization structure its APIs and governance," that's Platform Architect territory. If it's "which deployment, transaction approach or pipeline design meets these reliability and performance constraints," you're in this exam.
One more disambiguation. This is a MuleSoft credential. It has nothing to do with the Salesforce "Integration Architect" credential, which belongs to the Salesforce architect path and covers a different product set.
Section Weights and What Each One Tests
The outline in the guide has ten sections adding up to 100%.
| Section | Weight |
|---|---|
| Designing for the runtime plane technology architecture | 15% |
| Designing and developing Mule applications | 15% |
| Applying DevOps practices and operating integration solutions | 14% |
| Designing architecture using integration paradigms | 10% |
| Designing integration solutions to meet persistence requirements | 10% |
| Initiating integration solutions on the Anypoint Platform | 8% |
| Designing integration solutions to meet reliability requirements | 8% |
| Designing integration solutions to meet security requirements | 8% |
| Designing integration solutions to meet performance requirements | 7% |
| Designing automated tests for Mule applications | 5% |
Runtime plane architecture (15%). The objectives cover how a Mule runtime cluster differs from other deployment options, designing for CloudHub using its network features, when to use runtime domains, what class loader isolation in Mule 4 means for application design, and the reactive event processing model.
Designing and developing Mule applications (15%). The broadest section: application properties, fundamental features, core routers, the Salesforce Connector, core connector features, metadata sources in Transform Message, a Common/Canonical Data Model and data validation. It's design-flavored, but it assumes you can read a flow.
DevOps and operations (14%). A high-level CI/CD design using the MuleSoft-provided Maven plugins, automating interactions with Anypoint Platform, logging configuration across deployment options, and the features of Anypoint Monitoring.
Integration paradigms (10%). API-led connectivity, web APIs and HTTP, event-driven APIs with message brokers, and common messaging patterns.
Persistence (10%). VM queues with the Anypoint VM Connector, Object Stores and their connector and services, and stateful components that can use an Object Store, each one "in all deployment options."
Initiating solutions (8%). Functional versus non-functional requirements, choosing platform features for web and event-driven APIs, and control plane versus runtime plane deployment options.
Reliability (8%). Alternatives to traditional transactions, Until Successful, reconnection strategies, redelivery policies, disaster recovery versus high availability, and local and XA transactions for connectors that support them.
Security (8%). Secure access to the control plane and APIs, secure edge access with Anypoint Security, vulnerabilities in Mule applications, and audit logging.
Performance (7%). Meeting performance and capacity goals, streaming features and processing large sequences or streams of messages.
Automated tests (5%). MUnit unit test suites and deciding which requirements call for integration or performance testing.
A Study Order That Follows the Weights
Percentages tell you where the points are; dependencies tell you what to learn first. Here's a sequence that respects both.
- Initiating solutions (8%). It's short and sets the vocabulary: requirement types and the deployment options everything else refers to. Do it first.
- Integration paradigms (10%). Settle API-led, request-response and event-driven thinking before you drill into the runtime.
- Runtime plane architecture (15%). The first of your two largest blocks. Deployment topology shapes the answers in persistence, reliability and operations, so learn it early and revisit it often.
- Designing and developing Mule applications (15%). If you're a Developer-certified candidate, move through this quickly and spend the saved time on the Canonical Data Model and validation objectives. If you aren't, give it a full block and build a small flow for each router and connector the guide lists.
- Persistence, then reliability (10% + 8%). Study them as a pair. VM queues, Object Stores, transactions, Until Successful and redelivery policies are all answers to "what happens to this message when something fails," and the guide repeatedly asks you to answer it per deployment option.
- Performance and security (7% + 8%). Fewer objectives each, but both are trade-off sections where a technically valid design loses to one that meets a stated constraint.
- DevOps and operations (14%). The third-largest section, but it reads more naturally once you know what you're deploying and monitoring.
- Automated tests (5%). Last and lightest. Know what MUnit covers and when a requirement needs integration or performance testing instead.
Keep the final week for timed sets. Two hours for 60 questions is roughly two minutes each, and design scenarios with several defensible answers reward careful reading of the stated constraint over speed.
Practice for the MuleSoft Platform Integration Architect Exam on Certifyforce
The MuleSoft Platform Integration Architect practice exam page gathers the exam facts and section weights in one place. The free MuleSoft Platform Integration Architect questions are available now, each with an explanation, so you can find out which sections need work before you commit to a plan.
The full pack adds the reviewed question bank with timed exams and section practice. Practice exams are US$19, the study guide US$19, or both US$34 on the pricing page. The MuleSoft Platform Integration Architect study guide follows the same ten sections as the outline above.
Building a wider MuleSoft path? The MuleSoft Developer II guide covers the build-and-troubleshoot side, and the MuleSoft Developer guide covers the recommended starting exam.
Frequently Asked Questions
Is there a prerequisite for the MuleSoft Platform Integration Architect exam?
No. The exam guide lists the prerequisite as "None". It does recommend the Salesforce Certified MuleSoft Developer certification first, and it expects experience leading Anypoint Platform implementations.
How much does the exam cost, and what does a retake cost?
The exam guide lists US$400 to register and US$200 to retake, both plus applicable taxes. Fees can change, so confirm the figure when you book.
Is this the same as the Salesforce Integration Architect certification?
No. This is the MuleSoft Platform Integration Architect credential, built around Anypoint Platform and Mule applications. The Salesforce "Integration Architect" credential is a separate certification on a different path.
Which section should I study most?
Spend the most time on the two 15% sections, runtime plane architecture and designing and developing Mule applications, then the 14% DevOps and operations section. Together those three are 44% of the exam.
Does the certification need maintenance?
The exam guide says there is no required maintenance for this certification at this time. It encourages continued learning, so check the guide again before you rely on that.