The Short Answer
The Salesforce Certified MuleSoft Platform Architect exam has 60 multiple-choice questions plus up to five unscored, a 120-minute time limit, a 70% passing score, a US$400 registration fee (US$200 to retake) and no prerequisite. Questions align to the Spring '24 release (checked in November 2026 against the official exam guide).
This is the strategy exam of the MuleSoft track. It asks what an architect should recommend for an organization's Anypoint Platform, not how to write a flow. The largest section by far is governing web APIs (17%), and the nine sections are spread more evenly than on most exams, so no single topic carries you.
Exam Details at a Glance
Every figure below comes from the MuleSoft Platform Architect exam guide.
| Detail | MuleSoft Platform Architect |
|---|---|
| Questions | 60 multiple-choice, plus up to 5 unscored |
| Time limit | 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 |
| Release alignment | Spring '24 |
| Delivery | Proctored, at a testing center or online |
| References | No hard-copy or online materials during the exam |
Fees are subject to local taxes, so treat the guide as the source of truth at the moment you book. A retake costs half the first attempt, which is a good reason to arrive prepared rather than to use the first sitting as a diagnostic.
Who This Exam Is For
The guide describes candidates as people who define and are responsible for an organization's Anypoint Platform strategy. Typical roles are enterprise architects and solution architects with experience in common integration approaches such as SOA, plus basic knowledge of the platform's components.
There's no required certification before it. That's different from Developer II, which does require the first Developer exam, and it means the Platform Architect exam can be a first MuleSoft credential. In practice, it rewards two things: knowing the platform's parts well enough to pick between them, and having sat in the meetings where a team decides who owns an API, how it's secured and how it's monitored. If you've only built integrations, spend your hands-on time in API Manager and Runtime Manager rather than in Studio.
The hands-on route is also the guide's own advice. It recommends a mix of experience, training and self-study, and it names one Trailhead Academy course for this exam: Anypoint Platform Architecture: Application Networks (ARC720). If you'd rather start with free material, the MuleSoft Trailhead content on application networks and API-led connectivity covers the vocabulary the first sections assume.
Section Weights and What Each One Tests
The official outline has nine sections that add up to 100%.
| Section | Weight |
|---|---|
| Governing web APIs on Anypoint Platform | 17% |
| Designing APIs using System, Process, and Experience Layers | 12% |
| Monitoring and analyzing application networks | 12% |
| Architecting and deploying API implementations | 11% |
| Deploying API implementations to CloudHub | 11% |
| Establishing organizational and platform foundations | 10% |
| Designing and sharing APIs | 10% |
| Meeting API quality goals | 10% |
| Explaining application network basics | 7% |
Governing web APIs (17%). This is where API Manager lives: API instances and environments, choosing policies to meet non-functional requirements, proxy versus gateway enforcement, client ID and secret handling, access requests and approvals, OAuth 2.0 and identity providers, and when a custom policy is justified. The verbs in the guide are "select" and "explain", so expect scenarios where you pick the right policy for a layer.
Designing APIs by layer (12%). You assign APIs to system, process and experience layers by ownership, functional focus and rate of change, then decide how a system API's data model relates to its backend and whether to use an enterprise data model or bounded-context models.
Monitoring (12%). Which platform components produce monitoring data, what metrics are collected per API invocation, and which alerts to define for each layer and for Mule applications.
Architecting and deploying (11%) and CloudHub (11%). Auto-discovery, when you need a VPC, where MUnit fits against integration tests, DevOps automation, then CloudHub specifics: Object Store, worker sizes, shared versus dedicated load balancers, networking with customer VPCs and data centers, and avoiding single points of failure.
Organizational foundations (10%). A Center for Enablement (C4E) and the KPIs that show whether it works, MuleSoft Catalyst, hosting options for the control and runtime planes, identity and client management, and data residency.
Designing and sharing APIs (10%). Dependencies between an API, its specification, its implementation and its clients; publishing reusable assets; semantic versioning decisions; mapping between bounded contexts; idempotent HTTP methods and optimistic concurrency.
Quality goals (10%). Object Store versus caching, resilience strategies for API clients, and when horizontal scaling does or doesn't improve response time and throughput.
Application network basics (7%). The smallest section, but its concepts (the three tiers, the role of web APIs, the components of Anypoint Platform) are the language every other section is written in.
A Study Order That Follows the Weights
Weight tells you where the points are. Dependencies tell you what to learn first. This order balances the two:
- Basics first (7%). It's the smallest section, but you can't reason about layers or policies without it. Budget a short, early pass.
- Layers and API design (12% + 10%). Learn to place an API in a tier and justify it, then cover specifications, versioning and data-model mapping. These two sections share most of their ideas.
- Governance (17%). Your biggest block of points. Give it the most time, and build something: create an API instance, apply a rate limiting or client ID enforcement policy, and watch what changes in the specification and for the client.
- Deployment and CloudHub (11% + 11%). Treat these together. VPCs, load balancers, workers and Object Store all answer the same question: what does this deployment need to survive and perform?
- Quality goals (10%). Read it after deployment, because caching, resilience and scaling decisions depend on how the app is hosted.
- Monitoring (12%). Metrics and alerts make sense once you know what is being measured and where it runs.
- Organizational foundations (10%). It looks like the soft section, but the guide asks you to choose between hosting, identity and client-management options, not recite definitions. Study it last so you have the technical context to judge the trade-offs.
Leave the final week for timed practice. Two hours for 60 questions is roughly two minutes each, which is comfortable for short scenario items and tighter for questions with several plausible architectures. Note which answer you would have defended in a design review, then read the documentation behind every miss.
Practice for the MuleSoft Platform Architect Exam on Certifyforce
The MuleSoft Platform Architect practice exam page collects the exam facts and section weights in one place. The free MuleSoft Platform Architect questions are available now, with explanations, so you can test yourself on governance and layering scenarios before committing to a plan.
The full MuleSoft Platform Architect 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 Architect study guide covers the same nine sections as the exam outline.
If you're building a wider MuleSoft path, our MuleSoft Developer II guide covers the production-build side of the platform, and the MuleSoft Developer guide covers the entry-level developer exam.
Frequently Asked Questions
Is there a prerequisite for the MuleSoft Platform Architect exam?
No. The exam guide lists the prerequisite as "None". It does expect experience defining an organization's Anypoint Platform strategy.
How much does the exam cost, and what does a retake cost?
The exam guide lists a registration fee of US$400 and a retake fee of US$200, both plus applicable taxes. Check the guide when you book, because fees can change.
How many questions can I miss and still pass?
The guide publishes a 70% passing score for 60 scored questions. It doesn't publish an exact number you can miss, so aim well above the line rather than counting on a specific margin.
Which section should I study most?
Governing web APIs on Anypoint Platform, at 17% of the exam. Policies, enforcement approaches, client access and OAuth all sit there. The next largest sections, layered API design and monitoring, are 12% each.
What does the exam align to?
The guide says questions align to the Spring '24 release, so check the exam guide for updates before you sit the exam, and study current MuleSoft documentation for the topics it lists.