Most people build their Salesforce Platform App Builder study plan 30 days out by dividing the syllabus evenly across four weeks. Five domains, thirty days, six days each, done.
That's a bad plan, and the exam's own weighting tells you why: Business Logic and Process Automation is 28% of the exam — more than a quarter of your marks in a single domain — and it's the one that's changed most in the last two years. Split your time evenly and you're overspending on App Deployment (10%) while underspending on the section most likely to sink you.
Here's a plan weighted the way the exam is. If you want to calibrate before day one, sit some free Salesforce Platform App Builder practice questions cold and see which domain collapses.
First, the numbers
- 60 scored questions plus up to 5 unscored, multiple-choice and multiple-select
- 105 minutes
- Passing score: 63% — 38 of 60
- $200 registration, $100 retake
- No prerequisites, though it's usually taken after the Administrator cert
Official domain weighting:
| Domain | Weight |
|---|---|
| Salesforce Fundamentals | 23% |
| Data Modeling and Management | 22% |
| Business Logic and Process Automation | 28% |
| User Interface | 17% |
| App Deployment | 10% |
63% is a comparatively forgiving bar. But note what happens if you bomb Business Logic: lose most of 28% and you need near-perfection everywhere else to clear 63%. That domain is effectively pass/fail on its own.
What this exam is actually about (and how it differs from ADM-201)
The Administrator exam asks "how do you configure and maintain an org." App Builder asks "how do you design and build an app on the platform, declaratively."
The recurring theme is a line: declarative versus programmatic. Question after question describes a requirement and asks how to meet it. The correct answer is nearly always the declarative option — Flow, validation rule, formula field, roll-up summary — and Apex is the wrong answer unless the requirement genuinely can't be done clicks-only.
Know where that line sits. Cross-object updates that aren't parent-child, complex looping over large collections, callouts to external systems, unsupported roll-ups on lookups — those are the "now you need code" cases. Everything else has a declarative answer, and the exam wants it.
Days 1–5: Data Modeling and Management (22%)
Start here even though Fundamentals is listed first, because everything downstream depends on the data model.
- Relationships. Lookup vs master-detail vs many-to-many via a junction object vs hierarchical (User only). Know the consequences: master-detail cascades deletes, the child inherits the parent's sharing, and you get roll-up summary fields. Lookups don't. This is the highest-yield fact in the domain.
- Roll-up summaries — and the fact that they need master-detail. If a question wants a roll-up over a lookup, the answer is Flow (or a third-party declarative rollup tool), not a roll-up summary field.
- Schema Builder, external objects and external IDs, record types and how they interact with page layouts and picklist values.
- Field types you can't change later, and formula fields vs stored fields.
Build it, don't read it. Create a junction object between two customs, put a roll-up on a master-detail, then try to put one on a lookup and watch it not be there. Ten minutes, permanent knowledge.
Days 6–10: Salesforce Fundamentals (23%)
Broad, shallow, and full of free marks if you cover it.
Editions and their limits, licence types (Salesforce vs Platform — a recurring question shape: "which licence supports this?"), AppExchange, the difference between declarative and programmatic customisation, org-level setup, multi-currency basics, and general platform capabilities.
This domain rewards breadth over depth. Read widely, don't rabbit-hole.
Days 11–19: Business Logic and Process Automation (28%) — the long stretch
Nine days. This is the plan's whole point.
Flow is the centre of gravity. You need working fluency, not familiarity:
- Record-triggered flows: before-save vs after-save and why before-save is the performant choice for same-record field updates
- Scheduled flows, screen flows, autolaunched flows, platform event–triggered flows
- Decision elements, loops, collection variables, get/create/update/delete records
- Fault paths and error handling
- Entry criteria and the "only when a record is updated to meet the condition" option
Then the rest of the automation toolbox and when to pick each:
- Validation rules (and that they fire before save and can block automation)
- Formula fields, cross-object formulas, and their limits
- Approval processes — entry criteria, steps, initial submission actions, recall. The exam still tests these properly; they are not deprecated.
- Assignment and escalation rules
- Duplicate and matching rules
- Order of execution. Know it. Validation rules, before-save flows, after-save flows, workflow, triggers, roll-ups, escalation. Questions about "why didn't my automation see the updated value" resolve to order of execution.
And know the retirement story: Workflow Rules and Process Builder are out for new automation, Flow is in. Any resource that teaches Process Builder as current is stale.
Spend days 17–19 doing nothing but automation questions. This is where I found my gaps — I drilled sets on ExamCert because the questions are scenario-shaped like the real thing rather than definition trivia, and $4.99 for lifetime access with a money-back guarantee is a rounding error next to a $100 retake.
Days 20–24: User Interface (17%)
Lightning App Builder, record pages, dynamic forms and dynamic actions, component visibility rules, Lightning apps and utility bars, list views, compact layouts, path and highlights panel, page layout vs Lightning record page (two different things — the exam checks).
Also: Lightning vs Classic differences, and mobile considerations.
Dynamic Forms and component visibility come up a lot in modern versions of this exam. If your prep predates them, refresh.
Days 25–27: App Deployment (10%)
Smallest domain, quickest win. Change sets and their limits, deployment between sandbox types (Developer, Developer Pro, Partial, Full — and what data each carries), packages (unmanaged/managed/unlocked), what can and can't be packaged, and the basics of the Metadata API and SFDX.
Two days is genuinely enough. Don't overspend here.
Days 28–30: full-length timed runs
Three days, two or three complete timed attempts, and a rebuild of your miss list in between.
Rules for these final days: timed, no notes, no pausing. 105 minutes for 60 questions. If you're not clearing 75%+ consistently, move the booking — a two-week delay costs nothing, a retake costs $100.
For every miss, don't just note the right answer. Note why the option you chose solves a different problem. On this exam the distractors are all real features, so the skill being tested is discrimination between them. The AI simulator at ai.examcert.app explains that per-option reasoning, which is what turns a wrong answer into something you won't repeat.
The one-sentence version
Nine days on Business Logic, five on Data Modeling, two on App Deployment, and stop dividing your study time evenly across domains that aren't weighted evenly.
Take a free Platform App Builder practice test today, find out whether Flow is a strength or a hole, and start the thirty days from an honest number.
Top comments (0)