New to this track? Our Salesforce Certified MuleSoft Developer exam prep is the required first step. See our certification path to understand where this certification fits. The Salesforce Certified MuleSoft Developer II exam weights Implement performant and reliable Mule applications most heavily (27%), see the full breakdown, study tips, and practice questions below.
Free practice • No sign-up required
Independent study resource
Exam objectives and policies can change. Confirm current details with the certification issuer.
Check current objectives
Use the official exam guide as the source for current objectives and section weights.
Practice for learning
Use sample questions to review concepts and identify topics for further study.
Works on Any Device
Full practice experience on phone, tablet, or desktop
Free, No Sign-Up
Start practicing immediately, no account or email required
Salesforce Certified MuleSoft Developer II – Complete 2026 Guide
The advanced MuleSoft developer exam. Expect deep questions on DataWeave modules, batch processing, API security policies, CI/CD pipelines with Maven, and production deployment strategies. The exam is 60 scored questions in 120 minutes, with a 70% pass mark, weighted towards Implement performant and reliable Mule applications (27%) and Implement maintainable and modular Mule applications and Maven builds (25%).
Required Prerequisite
You must complete this certification before attempting this one.
| Official exam name and code | Salesforce Certified MuleSoft Developer II (MuleSoft Developer II) |
|---|---|
| Questions | 60 |
| Time allotted | 120 min |
| Passing score | 70% |
| Exam fee | $200 |
| Retake fee | $100 |
| Prerequisite certifications | Salesforce Certified MuleSoft Developer |
| Study guide release | Summer '26 |
Salesforce Certified MuleSoft Developer II Exam Weightage by Section
1. Expose production-ready Anypoint Platform-managed APIs (13%)
13%2. Implement maintainable and modular Mule applications and Maven builds (25%)
25%3. Implement monitorable Mule applications (15%)
15%4. Implement performant and reliable Mule applications (27%)
27%5. Secure data at rest and in transit (20%)
20%Exam Topics
Last updated:
Who is the MuleSoft Developer II exam for?
- Experienced MuleSoft developers: You’ve passed Developer I and want to validate your ability to build production-grade Mule applications independently.
- DevOps-focused integration engineers: You manage CI/CD pipelines for Mule apps and want to certify your Maven, MUnit, and CloudHub deployment expertise.
- Lead developers: You design advanced integration patterns and want the credential to back your architectural decisions on MuleSoft projects.
Exam Fees & Registration
Exam Fee
$200
One-time registration fee
Retake Fee
$100
If you need to retake the exam
Comparing certs? View all Salesforce exam fees in one place →
Certification Validity
Maintenance and renewal requirements vary. Check the issuer’s current credential page for requirements that apply to you.
How to Register
Check current Salesforce Certified MuleSoft Developer II credential and registration details with the issuer.
View official credential detailsOfficial references: Use the issuer’s current materials to confirm exam objectives, format, and fees before booking.
Official sources: Exam guide·Salesforce exam pricing·Independent exam-prep resource; details may change.
Exam Tips
- 1Advanced Mule Development is 30%. Know advanced Mule concepts, patterns, and best practices.
- 2Understand API Design and Security: RESTful APIs, OAuth, and API security.
- 3Know error handling and performance: error handling strategies and performance optimization.
- 4Be ready for "how do you develop X?" questions.
Prerequisites
- •MuleSoft Developer I
- •Advanced Mule development experience
Focus Areas
- •Advanced Mule Development
- •API Design and Security
- •Error Handling and Performance
- •Deployment and Operations
Study Strategy
Develop advanced Mule applications.
Design APIs, handle errors, optimize performance.
Align with the exam outline.
Exam Format and First-Attempt Readiness
The Salesforce Certified MuleSoft Developer II exam has 60 questions in 120 min, passing score 70%. Most Salesforce exams test scenario-based decisions. Focus on when to use each feature, not just terms.
- Study Implement performant and reliable Mule applications and Implement maintainable and modular Mule applications and Maven builds first, together they carry 52% of the exam.
- Do timed question sets. Build pacing and confidence.
- Review why wrong answers are wrong. It improves scenario reasoning.
- Book the exam once your mock scores are steady at 80%+.
Is the MuleSoft Developer II Exam Hard?
Is the MuleSoft Developer II Exam Hard?
MuleSoft Developer II is a hard exam. It assumes you already hold Developer I knowledge and tests advanced topics like batch processing, custom policies, CI/CD pipeline design, and production deployment strategies that require real project experience.
- 60 multiple-choice questions in 120 minutes.
- 70% passing score: the same threshold as Developer I, but the content is significantly more complex.
- Advanced DataWeave: expect pattern matching, custom modules, recursive functions, and complex nested transformations.
- Production experience matters: candidates with at least 6–12 months of hands-on Mule development in a production environment pass at significantly higher rates.
Pass Rate Guidance
Complete at least one production MuleSoft project with CI/CD before booking. Score 80%+ on practice exams since the real exam questions are more nuanced.
MuleSoft Developer II Exam Format Explained
MuleSoft Developer II Exam Format Explained
The exam is proctored online or in-person. Here is the format:
Total Questions
60 scored questions
Time Limit
120 min
Passing Score
70%
Question Type
Multiple-choice & multiple-select
How Many Questions Are Scenario-Based?
About 50–60% of questions are scenario-based. Common patterns include designing batch processing jobs for high-volume data, choosing the right API security policy combination, configuring CI/CD pipelines with Maven, and troubleshooting production deployment issues.
Best Way to Pass on Your First Attempt
- Go deep on DataWeave: Practice pattern matching, custom modules, and recursive transformations, the exam tests advanced syntax beyond basic map and filter.
- Build CI/CD pipelines: Configure Maven-based automated deployments to CloudHub and write MUnit tests with at least 80% coverage.
- Master batch processing: Know Batch Job phases, Batch Aggregator commit sizes, and how to handle failed records in high-volume data scenarios.
- Learn API security policies: Practice applying OAuth 2.0, JWT validation, rate limiting, and custom policies through API Manager.
MuleSoft Developer II: Key Concepts
Advanced DataWeave: Functions and Modules
DataWeave II advanced features: pattern matching (match/case for type-based branching), named functions (fun myFunc(arg) = ...), lambda functions (vars), and custom modules (import from external .dwl files). Complex scenarios: transforming nested arrays, handling nulls with default and orElse, type coercion. The exam presents complex transformation requirements and tests whether the developer can write efficient, readable DataWeave code, understanding when to use map vs reduce vs mapObject is critical.
Batch Processing in Mule
Batch Job scope processes large datasets in records. Phases: On Complete (runs after all records processed), On Input (optional pre-processing), Batch Steps (process each record). Batch Aggregator accumulates records before processing, commit size defines how many records are committed together. Failed records can be routed separately. Database.Stateful equivalent: use Batch Job Record Variables to carry state. The exam tests Batch Job configuration for high-volume data processing scenarios.
API Security: Policies and OAuth
Anypoint API Manager applies security policies to deployed APIs. Common policies: Client ID Enforcement (all clients must register and send client ID), OAuth 2.0 Token Enforcement (validate Bearer tokens), IP Allowlist, Rate Limiting (throttle by client or overall). Policies are applied through API Manager and injected into the runtime automatically, no code changes needed. The exam tests which policy combination to use for a given security requirement (authentication + authorisation + throttling).
Performance: Scatter-Gather and Cache Scope
Scatter-Gather executes multiple routes in parallel and aggregates responses, ideal for fan-out calls where all responses are needed. Each route runs concurrently; Scatter-Gather waits for all routes to complete before aggregating. Cache Scope stores responses for a configurable TTL, reduces redundant external calls. Reconnection strategies handle transient connectivity failures. Async processing (VM connector, queues) decouples processing speed from response time. The exam tests when each performance pattern is appropriate.
CI/CD with Anypoint: Maven and CloudHub Deployment
Anypoint Maven Plugin enables automated deployment in CI/CD pipelines. pom.xml configuration includes CloudHub credentials, region, and worker configuration. Anypoint CLI provides command-line deployment and management. API Autodiscovery links a deployed Mule app to an API definition in API Manager, enables policy enforcement. The deployment pipeline: unit tests (MUnit) → build JAR → deploy to CloudHub → run integration tests → promote to production. The exam tests CI/CD pipeline design and Maven plugin configuration.
A DataWeave script declares its output directive (e.g. %dw 2.0 output application/json), then maps the input payload, regardless of source format (JSON, XML, CSV), into the target structure using functions like map, filter, and pluck.
How to Pass the MuleSoft Developer II Exam
The MuleSoft Developer II exam tests advanced development skills: complex DataWeave transformations, async patterns, API security implementation, and advanced deployment strategies. Expect deep technical questions on Anypoint Platform internals.
Advanced DataWeave
Go beyond basic mappings: know how to use modules (Arrays, Strings, Math), pattern matching, recursive functions, and how to write reusable DataWeave modules. Know how to handle complex nested JSON and XML transformations.
Async & Batch Processing
Know Batch Jobs in Mule 4: Batch Job scope, Batch Step, Batch Aggregator, and On Complete phases. Understand when to use batch processing vs. scatter-gather for parallel processing of large data sets.
API Security Policies
Know how to apply policies in API Manager: Rate Limiting, JWT Validation, OAuth 2.0 (client credentials, authorization code), CORS, and IP whitelist. Understand policy ordering and how custom policies are built.
Advanced Deployment Strategies
Know the difference between CloudHub 1.0, CloudHub 2.0, and Runtime Fabric deployment models. Understand zero-downtime deployments, persistent queues, and how to configure multiple workers for HA.
Performance Tuning
Know how to tune thread pools (Grizzly, CPU intensive, CPU lite, I/O), configure watermark-based polling, and use caching (Object Store) to reduce redundant API calls in Mule applications.
Is the Salesforce Certified MuleSoft Developer II Exam Hard?
DifficultyChallenging; plan about 8-16 weeks of focused prep.
Book When ReadyScore 80%+ on three timed mocks before scheduling.
Use Practice, Not DumpsOriginal practice questions build skill without risking your credential.
Exam format: 60 questions, 120 min, 70% passing score.
Salesforce Certified MuleSoft Developer II Practice Questions (With Explanations)
Test your knowledge with these 15 sample questions.
Question 1: What is the focus of MuleSoft Developer II certification?
Key takeaway: MuleSoft Developer II validates ability to work on production-ready Mule applications and DevOps practices.
Show correct answer and explanation
Correct answer: A. Independently working on production-ready Mule applications in a DevOps environment
MuleSoft Developer II validates ability to work on production-ready Mule applications and DevOps practices.
- Developer II goes beyond basic APIs, it targets production-grade, DevOps-ready development.
- UI design is unrelated to MuleSoft Developer II's backend integration focus.
- Email development is unrelated to MuleSoft Developer II's integration focus.
Question 2: Which MuleSoft capability is used for complex data transformations?
Key takeaway: DataWeave is MuleSoft's transformation language for mapping and transforming data.
Show correct answer and explanation
Correct answer: D. DataWeave
DataWeave is MuleSoft's transformation language for mapping and transforming data.
- Apex is a Salesforce Core language, unrelated to MuleSoft data transformation.
- AMPscript is a Marketing Cloud personalization language, unrelated to MuleSoft.
- Visualforce is a Salesforce UI framework, unrelated to MuleSoft transformations.
Question 3: What is a best practice for error handling in Mule flows?
Key takeaway: Error handling scope and global error handlers provide consistent error handling and recovery.
Show correct answer and explanation
Correct answer: A. Use error handling scope and global error handler with appropriate strategies
Error handling scope and global error handlers provide consistent error handling and recovery.
- Apex try/catch is a Salesforce Core concept, not how Mule flows handle errors.
- Ignoring errors is the opposite of a best practice, it leads to unhandled failures in production.
- Deleting the flow doesn't address error handling at all.
Question 4: Which deployment target is commonly used for Mule applications in production?
Key takeaway: CloudHub and Runtime Manager (on-prem / hybrid) are used to deploy and manage Mule applications.
Show correct answer and explanation
Correct answer: C. CloudHub or Runtime Manager
CloudHub and Runtime Manager (on-prem / hybrid) are used to deploy and manage Mule applications.
- CPQ is a pricing/quoting tool, unrelated to Mule deployment targets.
- Slack isn't a deployment target for Mule applications.
- Email Studio is a Marketing Cloud tool, unrelated to Mule application deployment.
Question 5: What does reusable asset mean in API-led connectivity?
Key takeaway: Reusable assets are APIs and integrations designed for reuse across the organization.
Show correct answer and explanation
Correct answer: D. APIs designed to be reused across multiple projects and consumers
Reusable assets are APIs and integrations designed for reuse across the organization.
- Reusable assets are meant to serve multiple consumers, not just one.
- Reusable assets are designed for repeated use, not one-time use.
- Reusable APIs are software artifacts, not physical hardware.
Question 6: Which on-error strategy continues flow execution after an error?
Key takeaway: on-error-continue allows flow to continue after handling the error.
Show correct answer and explanation
Correct answer: A. on-error-continue
on-error-continue allows flow to continue after handling the error.
- Having no error strategy leaves failures unhandled, which isn't a valid Mule pattern.
- on-error-propagate stops flow execution and passes the error up, the opposite of continuing.
- 'on-error-delete' isn't a real Mule error-handling strategy.
Question 7: What is the purpose of batch processing in Mule?
Key takeaway: Batch processing handles large datasets in manageable chunks.
Show correct answer and explanation
Correct answer: D. To process large datasets in chunks
Batch processing handles large datasets in manageable chunks.
- Batch processing works with structured data, not specifically emails.
- Batch processing is about data volume, not API creation.
- Batch processing complements flows, it doesn't replace them.
Question 8: Which DataWeave function transforms an array?
Key takeaway: map, filter, pluck, and reduce transform arrays in DataWeave.
Show correct answer and explanation
Correct answer: B. map, filter, pluck, and reduce
map, filter, pluck, and reduce transform arrays in DataWeave.
- get is not a DataWeave array transformation function.
- set is not a DataWeave array transformation function.
- map alone doesn't cover the full range of array transformation functions DataWeave provides.
Question 9: What does API versioning support in MuleSoft?
Key takeaway: Versioning supports backward compatibility and migration.
Show correct answer and explanation
Correct answer: B. Backward compatibility and gradual client migration
Versioning supports backward compatibility and migration.
- Versioning specifically supports backward compatibility, so 'no support' is incorrect.
- Versioning is designed to avoid forcing breaking changes on all clients at once.
- Versioning supports gradual migration, not deprecation as its sole purpose.
Question 10: Which Mule component supports scheduled execution?
Key takeaway: Scheduler triggers flows on a schedule.
Show correct answer and explanation
Correct answer: B. Scheduler
Scheduler triggers flows on a schedule.
- 'On Error' handles exceptions, not scheduled execution.
- HTTP Listener responds to incoming requests, not scheduled triggers.
- Logger records messages, it doesn't trigger scheduled execution.
Question 11: What is the purpose of a custom policy in API Manager?
Key takeaway: Custom policies enforce custom logic on API requests.
Show correct answer and explanation
Correct answer: A. To enforce custom logic (e.g., rate limiting, validation)
Custom policies enforce custom logic on API requests.
- Policies enforce behavior; they aren't a deletion mechanism.
- Policies aren't limited to creation actions, they enforce ongoing rules like rate limiting and validation.
- Custom policies extend API Manager's capabilities, they don't replace APIs themselves.
Question 12: Which Mule scope supports transactions?
Key takeaway: Transactional scope ensures atomic processing.
Show correct answer and explanation
Correct answer: C. Transactional scope
Transactional scope ensures atomic processing.
- Transactions can span more than a single flow's local processing.
- 'Try' scope handles errors but doesn't provide transactional guarantees across multiple operations.
- Mule does support transactional scope; 'no scope' is incorrect.
Question 13: What does idempotency support in integration?
Key takeaway: Idempotency prevents duplicate processing on retries.
Show correct answer and explanation
Correct answer: B. Preventing duplicate processing from retries
Idempotency prevents duplicate processing on retries.
- Idempotency specifically addresses duplicate processing; 'no support' misstates its purpose.
- Idempotency is about correctness, not intentionally slowing down processing.
- Idempotency is about correctness (avoiding duplicates), not raw execution speed.
Question 14: Which deployment strategy supports zero-downtime on CloudHub?
Key takeaway: Blue-green and rolling deployments support zero-downtime.
Show correct answer and explanation
Correct answer: C. Blue-green or rolling deployment
Blue-green and rolling deployments support zero-downtime.
- Manual-only deployment doesn't inherently provide zero-downtime guarantees.
- A full restart causes downtime, the opposite of the zero-downtime goal.
- Having no deployment strategy risks downtime, which contradicts the goal of zero-downtime releases.
Question 15: What is the purpose of MUnit?
Key takeaway: MUnit is the testing framework for Mule applications.
Show correct answer and explanation
Correct answer: C. To unit test Mule flows and applications
MUnit is the testing framework for Mule applications.
- MUnit is for testing, not ongoing monitoring of running applications.
- MUnit specifically supports testing, not deployment.
- MUnit is a testing framework, not a replacement for Mule itself.
Get the Full Question Bank
Most candidates book the exam after scoring 80%+ on full mocks.
If you’re planning to test this quarter, aim to complete full mocks at least 10–14 days before your exam date.
Contact us for more information on our full 60-question mock exams and a personalized study plan. Use the contact form.
Request Mock Exams & Study PlanSalesforce Certified MuleSoft Developer II Exam FAQs
- What is covered on the Salesforce Certified MuleSoft Developer II exam?
- This page shows the section-wise exam weightage so you know exactly which topics carry the most weight. Use the exam topics and practice questions above to align your study with the official outline.
- What is the difference between MuleSoft Developer I and II?
- Developer I focuses on building basic Mule applications and APIs. Developer II covers advanced topics like error handling, performance optimization, API design patterns, and deployment strategies.
- Do I need MuleSoft Developer I before Developer II?
- While not strictly required, Developer I is highly recommended. Developer II assumes you have Developer I knowledge and builds on it with advanced concepts.
- Are there free practice questions for the Salesforce Certified MuleSoft Developer II exam?
- Yes. This page includes free sample practice questions with explanations. Use them alongside the current official documentation.
- How do I prepare for the Salesforce Certified MuleSoft Developer II certification?
- Use the exam tips, prerequisites, and study strategy on this page. Focus first on the highest-weighted sections, then take the sample practice questions. Schedule the exam when you consistently score well on practice tests.
Next Certifications After Developer
After this certification, common next steps in the developer track:
Honest Cert Breakdown
Difficulty: Hard
4/5Advanced DataWeave, performance optimization, and complex integration patterns. Requires solid MuleSoft Developer I experience as a foundation.
Salary Range
$115,000–$155,000 / year
US average for certified professionals • Updated Summer '26 • Source: Salesforce Talent Ecosystem
Is it worth it?
Good progression from MuleSoft Developer I. Opens senior developer and technical lead roles in integration-focused teams.
Section Breakdown
Section-by-Section Breakdown
Advanced Application Development
Advanced Mule 4 patterns: idempotent message filter, reliable messaging patterns, watermarking for batch processing. Advanced connectors (VM, Object Store, Anypoint MQ). Custom error handling strategies and global error handlers.
Advanced API Design & Governance
API governance with Anypoint Exchange, API versioning strategies, API Notebooks for documentation, custom policy development with PDK (Policy Development Kit), applying custom policies in API Manager.
Advanced DataWeave
Complex DataWeave transformations: recursive functions, type system, custom modules, output formats (multipart, binary), streaming large payloads, and performance optimisation of DataWeave scripts.
Security
Securing APIs with custom policies, OAuth 2.0 implementation, TLS/HTTPS configuration, secure properties encryption, Anypoint Secret Manager integration, and applying security best practices across environments.
Batch Processing & Performance
Batch job phases (Process Records, On Complete), batch processing for large datasets, watermarking for incremental processing, performance tuning for high-throughput integrations, and memory management.
8-Week Study Plan
How to Read Scenario Questions
- 1.Reliable messaging pattern: Use Anypoint MQ for durable, asynchronous message passing between Mule applications or to external systems. Use the VM connector for in-memory, within-application messaging (no external MQ required). Idempotent message filter prevents duplicate processing. Use with a correlation ID and Object Store.
- 2.Batch job phases: Process Records phase processes each record in parallel (configurable batch size). On Complete phase runs once after all records are processed. Use it for post-processing summaries, notifications, or cleanup. Error handling in batch is per-record, failed records go to failed records and do not stop successful records.
- 3.Watermarking implementation: On each run, retrieve the last watermark from Object Store → use it to query only new/updated records → process records → update the watermark in Object Store with the new max value. This ensures each run only processes incremental data.
- 4.Custom policy vs built-in policy: Use built-in policies (Rate Limiting, OAuth 2.0, IP Allowlist) when available; they are maintained by MuleSoft and require no code. Build a custom policy only when the requirement cannot be met by any built-in policy. The exam tests knowing when a custom policy is the right tool.
Readiness Benchmark
Aim for 80%+ on practice exams given the 70% passing score. Advanced Application Development (35%) is the heaviest section, master reliable messaging, Object Store, and Anypoint MQ before test day. Advanced DataWeave (20%) requires writing and reading complex expressions fluently.
10 Must-Know Concepts
- Reliable messaging: Anypoint MQ publish/subscribe, message acknowledgement, dead-letter queues
- Idempotent message filter: duplicate detection with correlation ID and Object Store
- Batch job phases: Process Records (parallel), On Complete (sequential post-processing)
- Watermarking: Object Store + Scheduler + incremental query pattern
- Advanced DataWeave: recursive functions, custom modules, streaming large payloads
- Secure properties encryption and Anypoint Secret Manager integration
- OAuth 2.0 enforcement via API Manager policies
- Custom policy development: PDK, DataWeave policy logic, policy YAML metadata
- TLS/HTTPS configuration in Mule 4 HTTP Listener
- API versioning strategies: URI versioning (/v1/api) vs header versioning
Common Questions
- What is the MuleSoft Developer II certification?
- The MuleSoft Developer II (MCIA-Level-2) certification validates advanced MuleSoft Anypoint Platform skills beyond Developer I. It covers advanced DataWeave, custom API policy development, batch processing, reliable messaging, security, and API governance. The exam has 60 questions, 120 minutes, 70% passing score, and a $200 fee. MuleSoft Developer I is a required prerequisite.
- What prerequisites are required for MuleSoft Developer II?
- MuleSoft Developer I (MCIA-Level-1) is a formal prerequisite; you must hold Developer I before you can sit Developer II. Beyond the formal requirement, strong real-world Mule 4 project experience is essential. Developer II tests advanced patterns that typically require 1–2 years of hands-on Anypoint Platform development experience after Developer I.
- What is watermarking in MuleSoft and why is it tested?
- Watermarking is a pattern for incremental data processing, tracking which records have already been processed so subsequent runs only process new or updated records. In MuleSoft, watermarking is implemented using the Object Store connector to persist the last processed timestamp or ID between flow executions. It is commonly combined with batch processing for large dataset integrations and is directly tested on Developer II.
- What is a custom policy in MuleSoft API Manager?
- Custom policies are reusable API governance rules applied to APIs via API Manager. They are built using the MuleSoft Policy Development Kit (PDK), writing policy logic in DataWeave and configuring policy metadata. Custom policies can enforce authentication, rate limiting, data transformation, logging, or any custom requirement that the out-of-the-box policies do not cover. Building and applying custom policies is a key Developer II topic.
- How long should I study for the MuleSoft Developer II exam?
- Plan for 8–10 weeks after MuleSoft Developer I, with 10–15 hours per week. Focus on the areas Developer I did not cover deeply: custom policies, advanced DataWeave (recursive functions, custom modules), batch job phases, Anypoint MQ reliable messaging, and the Object Store connector. All topics require hands-on sandbox practice in Anypoint Studio.
Where to Go Next
After this certification, consider: Platform Developer II, Platform App Builder, or JavaScript Developer I.
Topic Difficulty Heatmap
Which topics are a gimme vs which ones trap confident candidates. Use this to prioritise your final-week revision. These are our own topic groupings for study planning, not the official exam sections, those and their weightings are in the credential's exam guide.
| Topic | Difficulty | Study Tip |
|---|---|---|
| Advanced Mule Development | Hard | Error handling, batch processing, and reconnection, scenario-heavy. |
| API Design and Security | Trap ⚠ | Policies vs custom security, when to apply which at API vs proxy level. |
| Error Handling and Performance | Moderate | Fault handling and tuning. Know the default behaviours. |
| Deployment and Operations | Easy | Runtime Manager and deployment, factual if you have used the platform. |
Difficulty based on analysis of common candidate errors across each exam section.
Put It Into Practice
Test yourself with free MuleSoft Developer II practice questions.
Start Free Practice QuestionsTL;DR: What MuleSoft Developer II Tests
- API-led connectivity: Three-tier architecture (Experience, Process, System APIs), how to correctly layer business logic, API specifications with RAML, and the trade-offs of each architecture decision.
- Anypoint Platform management: CloudHub deployment, API Manager, API policies (rate limiting, client ID enforcement, OAuth), API Analytics, and environment management across development, staging, and production.
- Async messaging and batch: Anypoint MQ (queues, exchanges, message acknowledgement), batch processing (batch jobs, batch steps, on-complete phase), and when to use async patterns vs. synchronous flows.
Which Sections Carry the Most Weight
API-led + Platform Management + Anypoint MQ = 70%. Three-tier architecture design is the highest-value study area.
Scenario Strategy: How to Approach MuleSoft Developer II Questions
Questions describe an enterprise integration requirement and ask which architecture pattern, Anypoint component, or deployment approach is correct. Think about the three-layer API model first, which layer should own the logic described in the scenario?
- For API-led architecture questions: System APIs connect to core backends (SAP, databases, legacy systems), no business logic here. Process APIs orchestrate data from multiple System APIs and implement business logic. Experience APIs tailor output for a specific channel (mobile, web portal). Logic in the wrong layer = wrong answer.
- For Anypoint MQ questions: queues deliver to one consumer; exchanges (topic/fifo) can fan out to multiple subscribers. Acknowledgement modes: AUTO (ack on receive), MANUAL (ack after processing), NONE (no ack). Use MANUAL when you need guaranteed processing before acknowledging.
- For API policy questions: Rate Limiting throttles by request count per time window. Client ID Enforcement requires consumers to pass a client ID. OAuth 2.0 policy validates access tokens. Apply policies in API Manager, they attach to an API instance, not the Mule application code directly.
Booking Readiness Benchmark
80%+ on 3 timed full mocks before booking (70% passing score)
Developer II has a 70% passing score, the same as Developer I but with more complex architectural content. Real API-led project experience is important: candidates who have designed and implemented a three-tier MuleSoft architecture perform significantly better on the architecture design questions.
3 Concepts That Fail Most MuleSoft Developer II Candidates
These are not the hardest topics; they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. Batch Processing: Batch Job Phases and Error Handling
Mule Batch Jobs have three phases: Input (record collection), Process (on-record parallel processing), and On Complete (summary handling after all records are processed). Errors in the Process phase are per-record, a failed record does not stop other records from processing. Candidates design Batch Jobs expecting a single error to halt processing, the exam expects per-record error handling and the acceptPolicy setting that controls how failures affect the batch.
2. Async vs Sync Flow Execution: When Flow Runs Are Detached
By default, flows called via Flow Reference execute synchronously (in the same thread as the caller). Async scopes run a sub-flow asynchronously in a new thread, and the caller does not wait for the result. Candidates use Async scope expecting the caller to receive the async response; Async is fire-and-forget. Know when to use each based on whether the caller needs the processing result.
3. Watermark in Polling: Tracking Processed Records Across Runs
A Watermark in a Scheduler-triggered polling flow tracks the last-processed record (e.g., last timestamp) so subsequent runs only retrieve new or updated records. Without Watermark, every run re-processes all records. Candidates implement custom tracking variables for incremental polling, the exam expects the built-in Watermark feature with an Object Store for persistence across Mule runtime restarts.
Questions Candidates Ask
- What is the MuleSoft Developer II exam format?
- The MuleSoft Developer II exam has 60 multiple-choice questions, a 120-minute time limit, a 70% passing score, and a $200 fee ($100 retake). It tests advanced Mule 4 development: API-led connectivity, Anypoint MQ messaging, batch processing, custom API policies, and advanced DataWeave.
- What are the highest-weight MuleSoft Developer II exam sections?
- API-Led Connectivity (28%) and Anypoint Platform Management (22%) together account for 50% of the exam. Designing three-tier API-led architectures (Experience, Process, System), deploying to CloudHub, using Anypoint MQ for async messaging, and implementing API policies are the most heavily tested topics.
- What is API-led connectivity and why is it tested so heavily?
- API-led connectivity is MuleSoft’s recommended integration architecture pattern. It organises integrations into three layers: System APIs (connect to core systems like SAP, Salesforce), Process APIs (orchestrate business logic combining system APIs), and Experience APIs (tailored for specific consumer channels like mobile or web). The exam tests when to place logic at each layer.
- Do I need MuleSoft Developer I before Developer II?
- MuleSoft Developer I is the recommended (and effectively required) prerequisite for Developer II. Developer II assumes complete knowledge of Developer I content, flows, connectors, DataWeave, error handling, and builds advanced patterns on top. Candidates without Developer I knowledge will struggle significantly with Developer II material.
- What concepts do most MuleSoft Developer II candidates get wrong?
- The most commonly misunderstood topics for the MuleSoft Developer II exam are: (1) Batch Processing: Batch Job Phases and Error Handling; (2) Async vs Sync Flow Execution: When Flow Runs Are Detached; (3) Watermark in Polling: Tracking Processed Records Across Runs. Candidates are most confidently wrong on these. Learn the distinctions early to avoid losing marks on questions you expect to get right.
- Why do most Mulesoft Developer Ii candidates fail questions about Batch Processing?
- Mule Batch Jobs have three phases: Input (record collection), Process (on-record parallel processing), and On Complete (summary handling after all records are processed). Errors in the Process phase are per-record, a failed record does not stop other records from processing. Candidates design Batch Jobs expecting a single error to halt processing, the exam expects per-record error handling an...
- Why do most Mulesoft Developer Ii candidates fail questions about Async vs Sync Flow Execution?
- By default, flows called via Flow Reference execute synchronously (in the same thread as the caller). Async scopes run a sub-flow asynchronously in a new thread, and the caller does not wait for the result. Candidates use Async scope expecting the caller to receive the async response; Async is fire-and-forget. Know when to use each based on whether the caller needs the processing result.
- Why do most Mulesoft Developer Ii candidates fail questions about Watermark in Polling?
- A Watermark in a Scheduler-triggered polling flow tracks the last-processed record (e.g., last timestamp) so subsequent runs only retrieve new or updated records. Without Watermark, every run re-processes all records. Candidates implement custom tracking variables for incremental polling, the exam expects the built-in Watermark feature with an Object Store for persistence across Mule runtime r...
Related Study Resources
Start MuleSoft Developer II Prep
After this exam, consider Platform Developer II or Platform App Builder next.
Share or cite this study guide
Free to link from a forum post, study repo or article. Copy the Markdown and paste it anywhere.