Salesforce Platform Developer Exam Preparation Guide

A domain-by-domain preparation roadmap for the Salesforce Platform Developer exam: study sequence, hands-on practice, common mistakes and a readiness checklist.

Lucas Müller24 May 2026 · 10 min read

Ask AIChatGPT Claude Gemini Copilot Perplexity Grok

Desk illustration divided into four areas sized by Salesforce Platform Developer exam domain weightings, with code on screen

A surprising number of candidates begin preparing for "Platform Developer I" without realising the exam they are booking no longer carries that name. Salesforce dropped the "I" in its July 2025 renaming exercise, so the credential is now simply Salesforce Certified Platform Developer — the community still says "PD1", the content still targets working Apex and Lightning Web Components developers, and the exam guide (as of a check in August 2026) aligns questions to the Summer '25 release. If you hold the old-name credential, nothing changed for you; if you are preparing now, make sure every resource you use reflects the current outline, because the renamed exam also folded Agentforce concepts into its first domain.

This guide is a preparation roadmap: how to weight your revision across the four domains, what order to study in, how to practise hands-on, and how to know when you are ready to book. For the credential's position in the wider developer track — including Platform Developer II and the architect path it feeds — see the Salesforce Platform Developer certification guide, which owns that territory.

The exam you are preparing for, in numbers

Before planning anything, anchor your preparation to the format. As of 2026, the Salesforce Certified Platform Developer exam consists of 60 scored multiple-choice questions plus up to five unscored questions, taken in 105 minutes, proctored either online or at a testing centre. The passing score is 68%. Registration costs US$200 with a US$100 retake fee, plus applicable taxes, and prices vary by country — confirm current figures on the official exam guide before booking. There are no prerequisites, which surprises people who assume a coding credential must demand prior certification or a degree. It does not; it is, however, the required prerequisite for Platform Developer II.

Two planning consequences fall out of those numbers. First, 105 minutes for around 65 questions gives you roughly a minute and a half per question — enough time to read code snippets carefully, but not enough to re-derive governor limits from first principles. Fluency matters. Second, a 68% pass mark means you can miss almost a third of the questions; a weak domain is survivable, but two weak domains usually are not, which is why the weighting analysis below should drive your study calendar.

How the four domains should shape your revision

The current outline splits the exam into four domains. Treat the percentages as a revision budget, not trivia.

Process Automation and Logic — 28%. The largest domain, and the one where declarative and programmatic knowledge collide. Expect to reason about when Flow is the right tool versus Apex, how triggers behave in bulk, the order of execution, and how governor limits constrain design. If you write Apex daily but rarely touch Flow, this domain punishes that gap: questions frequently describe a business requirement and ask for the most appropriate automation, and "write a trigger" is often the wrong answer on the modern platform. Budget the largest single block of study time here, and split it deliberately between Apex logic (collections, SOQL/SOSL, exception handling, asynchronous patterns) and declarative automation.

Developer Fundamentals — 27%. Data modelling, object relationships, formula and roll-up behaviour, and — new since the 2025 refresh — Agentforce capabilities as they touch developers. Do not skip the Agentforce material because it feels peripheral; it now sits inside the exam's second-largest domain. Fundamentals questions reward people who have actually built objects and relationships in an org rather than memorised definitions, because they are usually phrased as "a developer needs to represent X — what should they use?"

User Interface — 25%. Lightning Web Components carry most of the weight, with Visualforce still present. You should be able to read a small LWC and predict its behaviour: component composition, event handling, wire adapters versus imperative Apex calls. If your background is pure back-end Apex, this is typically the domain that decides your result, and it is the hardest to fake — build components until reading them feels routine.

Testing, Debugging, and Deployment — 20%. Unit test requirements, test data patterns, debug logs, and how metadata moves between environments. Candidates from non-Salesforce backgrounds often find this the easiest domain because testing discipline transfers; long-time Salesforce developers who "write tests for coverage" sometimes discover the exam expects more principled answers about assertions and test isolation than their day job does.

A prioritised study sequence that matches the exam's logic

Study order matters more than total hours. A sequence that works for most candidates:

Read the official exam guide first and copy the outline into your own notes. Every later decision — what to study next, what to practise — should trace back to a line in that outline.
Secure a free Developer Edition org (or a Trailhead Playground). Every concept below should be tried, not just read.
Fundamentals before automation. Build a small data model of your own — three or four related objects — and exercise relationships, formulas and validation. Automation questions assume this foundation.
Apex core next: classes, triggers, SOQL, collections, bulkification, governor limits, then asynchronous Apex. Write a trigger, break it with a 200-record test, fix it. That single exercise teaches bulkification better than any summary table.
Declarative automation alongside Apex, not after it. For each requirement you implement in code, ask whether Flow could do it. The exam's favourite question shape is exactly that comparison.
Lightning Web Components as a project, not a topic. Build one component that calls Apex, raises events and composes a child component. Then read other people's components on Trailhead until prediction becomes easy.
Testing and deployment last, because writing tests for the code you built in steps 4–6 doubles as revision of everything else.
Timed practice at the end, once the outline holds no surprises — covered in its own section below.

Trailhead is free and remains the standard official preparation path; superbadges in particular force the hands-on work this exam rewards. If you want that sequence expanded into a week-by-week calendar, the Salesforce certification study plan covers scheduling in depth, and realistic timelines by experience level are the subject of our preparation time guide — this article deliberately stays on the what-and-in-what-order question.

Why an org beats a summary sheet

A realistic scenario: a Java developer with five years' experience decides to sit Platform Developer after three weeks of reading. She knows object-oriented programming cold, so Apex syntax poses no problem, and summary sheets make governor limits look memorisable. On exam day she meets a question describing a trigger that works in testing but fails on a bulk data load, followed by a question about which automation to choose for a cross-object update, followed by an LWC whose wire adapter she has read about but never used. Reading produced familiarity; the questions demand judgement, and judgement comes from having hit these walls in an org.

The pattern generalises. The exam's scenario style — "a developer needs to…", "what happens when…" — tests the consequences of platform behaviour, and consequences are what hands-on practice teaches cheaply. Every hour spent breaking and fixing your own code in a Developer Edition org is worth several hours of passive review, particularly for bulkification, order of execution and LWC behaviour.

Common mistakes that cost real attempts

Studying Apex and ignoring declarative tools. The platform's design philosophy — configuration before code — is itself examinable. Candidates who dismiss Flow as "admin stuff" leak marks across the largest domain.
Using pre-2025 study materials. Older resources miss the Agentforce additions and may reference outdated exam mechanics. Check any course or notes against the current official outline before trusting them.
Memorising governor limit numbers without the model behind them. Questions more often test what happens and how to design around limits than the raw figures.
Skipping Visualforce entirely. LWC dominates the User Interface domain, but Visualforce has not vanished from it.
Treating test coverage as the goal of testing. Expect questions where the technically-passing, assertion-free test class is a wrong answer.
Booking on a first strong practice score. One good run proves less than a stable trend — see the next section.

Reading code under time pressure: an exam-day skill worth training

Platform Developer questions lean heavily on code comprehension: a snippet of Apex or an LWC template followed by "what happens?" or "what should the developer change?". Reading unfamiliar code accurately at speed is a distinct skill from writing it, and it is trainable. During your final weeks, practise a three-pass routine on every code question you meet: first identify what the code is for (trigger, batch class, test method, component), then trace the data — what enters, what is queried, what is modified — and only then evaluate the answer options against that trace. Candidates who jump straight to the options get anchored by plausible-looking distractors, especially on bulkification questions where the single-record behaviour is correct and the 200-record behaviour is the trap.

Pacing follows the same discipline. With roughly 95 seconds per question, a fair rule is: answer what you know immediately, move past anything that needs more than two minutes, and return with the time saved — a clear head on a second pass resolves more doubtful questions than stubbornness on the first. Long scenario stems reward reading the final sentence — the actual question — before the scenario itself, so you know what to look for on the way through.

One more exam-day note: whether you sit at a testing centre or online, the format is identical, but online proctoring adds environment checks and stricter desk rules. If your home workspace is noisy or shared, a testing centre removes a variable you do not need on the day.

Using practice questions to find out where you actually stand

Practice questions serve one purpose in this plan: measurement. After finishing the study sequence, take a full-length, timed practice run and score it by domain against the outline. A result such as "strong on Testing, 55% on User Interface" converts directly into a revision instruction in a way that an overall percentage never does. Then target the weak domain, rebuild the relevant material hands-on, and re-test. Avoid re-taking the same question set repeatedly — recognising answers is not the same as understanding objectives, and the real exam will paraphrase.

ExamPractice offers free sample Salesforce Platform Developer practice questions, with fuller question sets and a timed practice-test simulation available to subscribers; the broader Salesforce exams hub covers the rest of the track. For technique — how to schedule mock exams and read the results — the Salesforce practice test guide is the dedicated resource.

A readiness checklist before you book

Book the exam when you can honestly tick every line:

I can explain the order of execution and predict what a described trigger-plus-flow combination will do.
I can look at a business requirement and justify Flow, Apex or a combination — and say why the alternatives lose.
I have written a bulkified trigger and a test class with meaningful assertions, unaided.
I can read an unfamiliar LWC and describe its data flow, including wire versus imperative Apex.
I know how changes move between environments and what each deployment option is for.
I have covered the Agentforce material in Developer Fundamentals, not just legacy notes.
My last two timed practice runs scored comfortably above 68% with no domain badly lagging.
I have confirmed the current fee, format and release alignment on the official exam guide.

Booking day, and what comes after

When the checklist holds, book promptly — readiness decays, and a fixed date focuses the final fortnight. Choose online proctoring or a testing centre according to your tolerance for at-home exam conditions, and spend the last days on light domain review rather than new material. Afterwards, the credential stays active through Salesforce's free Trailhead maintenance modules rather than a paid recertification cycle — the certification renewal guide explains the deadlines. Many developers then progress to Platform Developer II, for which this certification is the required prerequisite; and if you are still weighing whether the developer track suits you better than the admin route, that decision has its own comparison article. Prepare in the order the exam is weighted, practise in an org rather than on paper, and the 68% bar is a fair one for a working developer to clear on the first attempt.

Frequently asked questions

Is Platform Developer I still a valid certification name?

The credential earned under the old name remains fully valid — Salesforce renamed 35 certifications in July 2025 and holders' credentials updated automatically, with no retake required. New candidates register for "Salesforce Certified Platform Developer"; job adverts and community posts will keep saying PD1 for years.

Do I need to know Java or another language before preparing?

No formal prerequisite exists. Prior object-oriented programming experience shortens the Apex learning curve considerably, but plenty of candidates arrive from admin backgrounds and succeed by spending longer in the fundamentals and logic domains.

How many questions can I get wrong and still pass?

With 60 scored questions and a 68% passing score, you need roughly 41 correct — about 19 wrong answers of headroom. Unscored pilot questions (up to five) do not count either way, and you cannot tell which they are.

What does a retake cost if I fail?

US$100 plus applicable taxes, against the US$200 first attempt — pricing varies by country, so confirm on the official guide. Treat a failed attempt as a diagnostic: compare it against your domain-scored practice results to decide where to rebuild before paying again.

Exam facts in this guide were checked against official certification-provider pages on 30 August 2026. Fees, exam codes and policies change — confirm on the provider’s own site before you book.