CF
home

MuleSoft Platform Architect Study Guide

The Certifyforce MuleSoft Platform Architect study guide covers the official Salesforce MuleSoft Platform Architect exam outline in 47 units across all 9 exam sections, one unit per exam-guide topic. The exam itself has 60 scored questions plus 5 unscored, a 120-minute limit and a 70% passing score, and its largest section is Governing web APIs on Anypoint Platform at 17%. Every unit is verified against official Salesforce documentation, cites its sources, and links to the practice questions that test it.

Define an Anypoint Platform strategy through API-led connectivity, platform governance, deployment choices and operational architecture.

47 lessons · 9 exam sections · about 5 h of reading

Turn your section feedback into a study plan
Exam sections

Unlock the full guide

Every lesson's summary, exam expectations, key facts and self-check questions are free to read. The MuleSoft Platform Architect 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.

Already own it? Sign in

Explaining application network basics

7% of the exam
  1. API Led Connectivity Technologies~5 minSeparate API descriptions, implementation building blocks and runtime management, then use metadata deliberately when designing Mule integrations.
  2. Web API Contracts and Characteristics~5 minIdentify the network contract a web API exposes, choose interactions by resource intent, and distinguish each transport boundary from the implementation behind it.
  3. API Tier Ownership and Change~5 minClassify APIs by the responsibility they expose, then interpret ownership and change as supporting evidence rather than automatic tier labels.
  4. Anypoint Platform Component Responsibilities~6 minLocate design, discovery, implementation, API management and application operations responsibilities, and distinguish catalogue evidence from a running service.

Establishing organizational and platform foundations

10% of the exam
  1. C4E Enablement and Success Measures~6 minAssess C4E readiness, define its operating model and connect shared assets with evidence of organizational delivery improvement.
  2. Catalyst Delivery and Operating Model~7 minUse Catalyst's playbook paths and integrated blueprint to connect business outcomes with platform adoption, delivery and a sustainable operating model.
  3. Control Planes and Runtime Hosting~7 minChoose compatible control and runtime hosting, assign infrastructure and recovery ownership, and distinguish regions, compliance boundaries and server registration.
  4. Platform Identity and Client Management~7 minSeparate organization-user SSO from API-consumer registration, then configure federation, provisioning and OIDC client-provider capabilities in their proper scopes.
  5. Data Residency Across Platform Services~8 minTrace payloads, metadata, logs, metrics and persistent state to their actual service locations, including the effects of regional moves, failover and log lifecycle changes.

Designing and sharing APIs

10% of the exam
  1. API Contracts and Dependency Boundaries~6 minTrace the contract, repository dependency and implementation separately, then identify which teams must act when each changes. Use Studio's design tools without confusing a specification reference with application code.
  2. Reusable Assets and Exchange Publication~7 minPublish API specifications and reusable fragments with explicit identities, dependencies and lifecycle choices. Distinguish a reusable design artifact from an API Group package and its environment-specific instances.
  3. API and Asset Version Compatibility~7 minClassify API changes by their effect on existing consumers, then keep the contract version and Exchange asset release consistent. Review behavior, data, representations and access as well as schemas.
  4. Bounded Context Relationships and Power~6 minChoose context-mapping strategies from delivery dependence, influence and model ownership. Use a realistic context map to distinguish coordination, shared models, upstream conformity and protective translation.
  5. Idempotent Requests and Concurrent Updates~6 minSeparate safe reads, repeatable request effects and conditional updates. Use HTTP validators to distinguish existence checks, lost-update protection and cache revalidation.

Designing APIs using System, Process, and Experience Layers

12% of the exam
  1. Business Processes Across API Layers~7 minDecompose a business process into reusable responsibilities, preserve dependencies between calls, and avoid extra application hops that add no business value. Use the documented simplification guidance to review the resulting design.
  2. Layer Responsibilities and Team Ownership~7 minAssign business and technical accountability according to the capability, shared semantics, consumer relationship and expected change impact. Preserve stewardship as teams, versions and organizational needs evolve.
  3. System API Models and Backend Isolation~7 minChoose a System API representation from the required abstraction and existing contracts. Preserve business semantics and identifier perspectives while using model-driven design to keep the agreed model useful in implementation.
  4. Enterprise and Bounded Context Models~7 minChoose model scope from shared meanings and ownership, then preserve explicit interchange boundaries where contexts differ. Keep the model useful through hands-on collaboration between domain experts, modelers and implementers.
  5. DataGraph Composition and Runtime Behavior~7 minAssess DataGraph as a managed composition interface over reachable REST implementations. Distinguish links, enrichment and schema consolidation, then plan mutations, usage allocation and persisted-query caching without assuming it replaces provider behavior.

Governing web APIs on Anypoint Platform

17% of the exam
  1. API Instances Across Environments~6 minChoose environment boundaries for managed API instances, distinguish promotion from deployment and plan permissions and consumer transitions.
  2. Policies for Nonfunctional API Requirements~7 minSelect gateway controls for traffic, request structure and metadata, separating hard consumption limits, burst smoothing and browser-visible feedback.
  3. API Specifications and Policy Contracts~7 minAlign API specifications with configured policy inputs, accepted token and payload forms, intercepted methods and gateway-generated responses.
  4. Gateways Proxies and Service Mesh~6 minCompare embedded gateways, proxies, historical Service Mesh and Spring 2024 Flex modes while preserving runtime and policy compatibility boundaries.
  5. Security Across API Led Layers~7 minChoose layer-appropriate browser, token, scope and application-contract checks, preserving authenticated identity through policy composition.
  6. Client Credentials and API Contracts~7 minSend application credentials according to the selected enforcement policy while separating user authentication, runtime identity and instance-specific contracts.
  7. API Access Requests and Contract Lifecycle~7 minRequest and approve the intended application's API access, review tier changes and alternative group grants, and choose scoped revocation, restoration or deletion.
  8. Security Policy Selection and Enforcement~7 minMatch security policies to credential types, provider relationships and enforcement requirements, including token freshness, directory search, trusted network identity and rotating verification keys.
  9. Identity Providers and OAuth Client Boundaries~7 minSeparate platform-user identity from API-client management, bind providers across business-group environments and API instances, and plan provider transitions, registration credentials and discovery.
  10. Custom Policy Packaging and Execution~7 minChoose reusable custom-policy behavior, separate deployable assets and runtime boundaries, and check message propagation, dependency compatibility and built-in policy context.

Architecting and deploying API implementations

11% of the exam
  1. API Autodiscovery and Runtime Registration~6 minPair a Mule implementation with its managed API instance using the correct instance identifier, credential scope and runtime configuration.
  2. VPC Requirements and Network Boundaries~7 minChoose classic CloudHub VPC boundaries, ownership and worker access controls while keeping network placement separate from environments and load balancers.
  3. Runtime Hosting and Deployment Management~7 minManage API implementations across CloudHub, hybrid servers and Runtime Fabric, distinguishing deployment ownership, application state and operational tools.
  4. MUnit Test Scope and Isolation~7 minSet MUnit boundaries for isolated flow tests and real integration checks, with explicit source lifetime, mocking prerequisites and validation evidence.
  5. Automated Build Test and Deployment~7 minAutomate packaging, MUnit execution and deployment with explicit artifact, target, identity and verification boundaries.

Deploying API implementations to CloudHub

11% of the exam
  1. Object Store Use on CloudHub~6 minChoose Object Store v2 for keyed CloudHub integration state, budget application-wide calls and inspect value limits, partitions and lifecycle boundaries.
  2. CloudHub Worker Sizing and Configuration~7 minSize classic CloudHub workers by sustained compute, heap and disk, then plan bounded autoscaling against available account capacity.
  3. CloudHub Worker Recovery and Reliability~7 minPredict classic CloudHub workload distribution, queue and connection behavior, and the recovery dependencies that constrain updates and regional plans.
  4. Shared and Dedicated Load Balancers~7 minSelect classic CloudHub entry services by certificate, routing and rate requirements, then account for DLB DNS transitions, buffering and administration.
  5. CloudHub Connectivity to Customer Networks~7 minCompare classic CloudHub private connectivity methods and validate routing, endpoint capabilities, shared route budgets and VPN limitations.
  6. Failure Domains and Disaster Recovery~7 minMatch classic CloudHub recovery designs to tunnel, gateway, site and regional failures, and distinguish application restart settings from infrastructure recovery.

Meeting API quality goals

10% of the exam
  1. Caching and Object Store Design~7 minChoose temporary state and caching boundaries, configure coherent Mule cache access and sharing, and apply HTTP freshness, validation, invalidation and explicitly permitted stale reuse.
  2. Client Resilience and Retry Boundaries~7 minBudget complete API attempts and recovery, prevent retry amplification, separate connector retry mechanisms and combine compatible fallbacks with resource isolation and failure-state controls.
  3. Horizontal Scaling and Backend Capacity~7 minLocate client, API and backend bottlenecks before promising scale-out gains; budget replica connection pools, externalize worker-dependent state and validate representative performance tests.

Monitoring and analyzing application networks

12% of the exam
  1. Observability Data and Collection Boundaries~8 minIdentify application, API and agent data producers, then configure custom measurements and diagnostic logs within their collection and access boundaries.
  2. API Metrics and Aggregation Semantics~6 minInterpret API metrics, report fields and time windows without confusing chart presentation, retained telemetry or environment scope with business evidence.
  3. API Alerts and Tier Specific Signals~7 minConfigure API-led alert populations and layer budgets while respecting sliding windows, state changes, notification scope and automated-policy limits.
  4. Mule Application Alerts and Operations~7 minSelect deployment-specific Mule application and server alerts, interpret their counters and resource scope, and configure actionable shared notifications.

Common questions about the MuleSoft Platform Architect study guide

Is the MuleSoft Platform Architect 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 Platform Architect pack (USD $19).

How current is the MuleSoft Platform Architect study guide?

It is written to the current official Salesforce MuleSoft Platform Architect exam outline, and each unit is checked against Salesforce documentation before it is published.

How does the study guide map to the official MuleSoft Platform Architect exam guide?

There is one unit per topic in the official exam guide, grouped under its 9 weighted sections: Explaining application network basics (7%), Establishing organizational and platform foundations (10%), Designing and sharing APIs (10%), Designing APIs using System, Process, and Experience Layers (12%), Governing web APIs on Anypoint Platform (17%), Architecting and deploying API implementations (11%), Deploying API implementations to CloudHub (11%), Meeting API quality goals (10%), Monitoring and analyzing application networks (12%). 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 (300 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.