Updated for Winter '26
PD1 Exam Tips (Winter '26): How to Pass Platform Developer I First Attempt
Platform Developer I (PD1) is Salesforce's most code-intensive associate-level cert. These tips focus on the areas that trip up candidates most: governor limits, bulkification, and the 75% code coverage requirement.
Written and reviewed by Krishna Mohan — ADM-201, PD1, PD2, App Builder & Consultant certified. Updated for Winter '26. Methodology · Contact
Exam At a Glance
60
Questions
105 min
Time Limit
65%
Passing Score
$200
Exam Fee
Quick Answer: Best Way to Pass PD1
- Logic and Process Automation is 28% of the exam — master Apex triggers, governor limits, and async patterns first.
- Write real Apex code every day. PD1 scenarios require you to identify bugs and select correct patterns, not just recall facts.
- Take timed mocks (60 questions / 110 minutes). You are ready when you consistently score 78%+ — the passing score is 68%.
PD1 Exam Weightage at a Glance
Focus time proportionally. The top three sections cover 73% of the exam.
Apex, triggers, async (Future, Batch, Queueable)
Platform concepts, data model, security model
SOQL, SOSL, DML, relationships, schema
75% coverage rule, Test.runAs(), debugging tools
LWC basics, @AuraEnabled, Lightning Data Service
Governor Limits You Must Know Cold
PD1 tests governor limits directly and through scenario questions. Memorise these before exam day:
| Limit | Synchronous | Asynchronous |
|---|---|---|
| SOQL queries per transaction | 100 | 200 |
| DML statements per transaction | 150 | 150 |
| Records per DML operation | 10,000 | 10,000 |
| Total records retrieved by SOQL | 50,000 | 50,000 |
| Apex CPU time | 10,000 ms | 60,000 ms |
The exam will ask you to identify code that violates these limits — especially SOQL/DML inside for loops.
4-Week PD1 Study Plan
Week 1 — Salesforce Fundamentals & Data Modeling (45%): Platform data model, object relationships (lookup vs master-detail), field types, schema builder, SOQL (relationship queries, aggregate functions, dynamic SOQL), SOSL, and DML operations.
Week 2 — Logic and Process Automation (28%): Apex fundamentals, trigger events (before/after, isNew, isUpdate, isDelete), bulkification patterns, governor limits, async Apex (Future, Batch, Queueable, Scheduled), and error handling.
Week 3 — Testing, Deployment & UI (27%): Writing @isTest classes, Test.startTest()/stopTest(), Test.runAs(), mock data, 75% coverage requirement, debugging logs, changeset/metadata deployment, and LWC fundamentals (@api, @wire, @AuraEnabled).
Week 4: Full timed mock exams (60 Q / 110 min), weak-area targeted revision, and final review of governor limit scenarios before booking.
How to Handle PD1 Scenario Questions
Most PD1 questions give you a code snippet or business requirement and ask you to identify the problem or select the best implementation. Two strategies work here:
- Code review questions: Look for DML or SOQL inside a loop first — that is the most common governor limit trap. If you see it, the answer involves moving operations outside the loop.
- Requirement questions: Map the requirement to the right async tool. Use Future for single-record callouts, Batch for large data volumes, Queueable for chaining jobs, and Scheduled for time-based execution.
- Testing questions: If the scenario asks about code coverage or test data, remember: 75% overall is required, @TestVisible exposes private members, and Test.runAs() tests user-context behaviour.
Mock-Test Benchmark Before Booking
PD1 passing score is 68% (41/60 questions). Use this benchmark before scheduling:
78%+ on 3 timed full mocks (60 Q / 110 min), one week apart
The 10-point buffer above the passing score accounts for first-attempt nerves and unfamiliar question phrasing. If you are failing the Logic & Process Automation questions consistently, spend another week on triggers and async Apex before booking.
3 Concepts That Fail Most PD1 Candidates
These are not the hardest topics — they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. SOQL Inside For-Loops: The Governor Limit That Kills Your Score
The 101-query governor limit means any SOQL statement inside a loop will fail at runtime when processing more than 100 records. Exam scenarios show code snippets and ask you to identify the bug. The wrong-answer trap is selecting “reduce batch size” — the correct fix is always “move the SOQL outside the loop and use a Map or List.” Train yourself to scan every for-loop in a code snippet and ask: is there a SOQL or DML statement inside?
2. @wire vs @api vs @track: One Wrong Decorator, One Wrong Answer
LWC decorator questions are a guaranteed exam topic. @wire connects a property to a Salesforce data service (Apex or UI API) reactively. @api exposes a property or method to a parent component — it is public. @track is largely deprecated in modern LWC; plain properties are now reactive by default. The trap: candidates use @track thinking it makes a property “reactive” when @wire is what actually connects to the server.
3. Test Classes: Coverage Is Not Enough — Assertions Are Required
A test class that runs code and hits 75% coverage but contains no System.assert() statements is considered invalid for certification purposes. Exam questions often show a test method and ask what is wrong — the correct answer is “no assertions” even if coverage looks sufficient. Also know: callout mocks require HttpCalloutMock implementation — calling a real endpoint in a test will throw an exception, not just fail silently.
Frequently Asked Questions
What is the PD1 exam format?
What are the highest-weight PD1 topics?
How long does it take to prepare for PD1?
What is the hardest part of the PD1 exam?
What concepts do most PD1 candidates get wrong?
Why do most PD1 candidates fail questions about SOQL Inside For-Loops: The Governor Limit That Kills...?
Why do most PD1 candidates fail questions about @wire vs @api vs @track: One Wrong Decorator, One Wr...?
@wire connects a property to a Salesforce data service (Apex or UI API) reactively. @api exposes a property or method to a parent component — it is public. @track is l...Why do most PD1 candidates fail questions about Test Classes: Coverage Is Not Enough?
System.assert() statements is considered invalid for certification purposes. Exam questions often show a test method and ask what is wrong — the correct answer is "no assertions" even if coverage looks sufficient. Also know: callout mocks require Related Exam Tips
Next Step
Apply these tips with real exam-style practice questions:
After this exam, consider Platform Developer II or Platform App Builder next.