MuleSoft Certification Bootcamp: Developer & Architect Exams (Course #cert-bootcamp)

Programme every line is something you do

6 modules · 18 topics · in course-flow order

1. Module 1

   Four credentials, one roadmap

   Objective. Diagnose which of the four current credentials each engineer should sit and produce the cohort's dated booking roadmap.

   • Assign each of the 24 candidates one target credential — Salesforce Certified MuleSoft Developer, Developer II, Platform Architect or Platform Integration Architect — and write the one-line reason next to the name; Salesforce publishes no short exam codes, so any “MCD”- or code-styled study material is stale by definition
   • Read the exam envelope before opening a single lesson: 60 scored questions plus up to five unscored, 120 minutes, 70 % pass mark — 2 minutes per question with nothing spare — US$400 to register, US$200 to retake
   • Lay the roadmap on a calendar: diagnostic in week 1, weighted drill blocks in weeks 2–5, mock gated at 65 %, exam slot booked inside 8 weeks
2. Module 2

   Score your gaps by weight

   Objective. Evaluate each candidate's confidence domain by domain against the published weightings and rank study effort by weight multiplied by gap.

   • Self-score 0–5 on all 12 Developer exam domains and the 5 Developer II exam domains, then multiply each score gap by the published weight to rank where the hours go
   • Attack the heavy blocks first: Performant & Reliable Apps at 27 % and Maintainable Apps at 25 % are over half of the Developer II exam on their own
   • Set the abandon line explicitly — any domain under 60 % earns a dated drill block, anything above 85 % gets a 20-minute review and no lesson
3. Module 3

   Developer domains under the clock

   Objective. Construct defended answers on the highest-weighted Developer exam domains and log the elimination reasoning for every scenario stem.

   • Drill the five 10 % domains that carry half of the Developer exam — accessing and modifying Mule events, structuring apps, connectors, processing records, transforming data with DataWeave 2.x
   • Rehearse routing, error handling and designing APIs — 8 % each, 24 % together — by striking two distractors out loud before re-reading the stem
   • Refuse to over-study the light domains: Debugging is 5 %, roughly 3 questions of 60, so it gets one 30-minute block and no more
4. Module 4

   Developer II: production-grade code

   Objective. Design the answer patterns for the two heaviest Developer II exam domains and record one worked justification per pattern.

   • Work the 27 % Performant & Reliable block: streamed payloads over in-memory, caching scopes, retry with backoff, Anypoint MQ redelivery and DLQ behaviour
   • Cover Data Security at 20 % — secure properties, TLS contexts, field-level tokenization — and name which control answers which threat
   • Instrument for the 15 % monitorable block with correlation IDs, custom metrics and Anypoint Monitoring alerts, then write the 13 % production-readiness answer that ties them together
5. Module 5

   Two architect exams, one estate

   Objective. Arbitrate between the two architect credentials per candidate and drill each blueprint's heaviest domains against the Verdanis estate.

   • Separate the blueprints before studying either: the Platform Architect exam puts 17 % on governing web APIs and 12 % on designing APIs across System, Process and Experience layers, while the Platform Integration Architect exam puts 15 % each on runtime-plane architecture and designing Mule applications
   • Drill the operational third of the Platform Architect exam — 11 % architecting and deploying implementations, 11 % deploying to CloudHub, 12 % monitoring and analyzing application networks — knowing the CloudHub domain examines classic CloudHub: worker sizes, the shared worker cloud, Shared vs Dedicated Load Balancers and customer Amazon VPCs, not the private spaces Verdanis runs
   • Cover the Platform Integration Architect exam where it pays: 14 % DevOps and operations, 10 % persistence, 8 % reliability; automated tests at 5 % gets a checklist, not a lab — and remember the Developer credential is recommended, not required, for this exam
6. Module 6

   Timed mock, honest debrief

   Objective. Prove readiness with a full mock sat under exam conditions and convert the per-domain score into a booking decision with a date on it.

   • Sit the full mock cold: 60 questions in 120 minutes, flag and move on anything still open after 3 minutes, no more than 8 flags carried into the review pass
   • Debrief by domain rather than by total: 65 % overall is the floor to book, and any weighted domain under 60 % blocks the slot regardless of the total
   • Rehearse exam-day mechanics — proctored check-in, multi-select stems answered by elimination, the flagged-question sweep in the final 15 minutes

References & Official Documentation every claim above has a source

Across the course

• Anypoint Monitoring OverviewMuleSoft Docs

Module 3

• Batch ProcessingMuleSoft Docs
• DataWeave OverviewMuleSoft Docs
• Error HandlersMuleSoft Docs

Module 4

• Secure Configuration PropertiesMuleSoft Docs
• Streaming in Mule AppsMuleSoft Docs

Module 5

• Anypoint API Governance OverviewMuleSoft Docs
• CloudHub 2.0 OverviewMuleSoft Docs