Updated for Winter '26
PD2 Exam Tips (Winter '26): How to Pass Platform Developer II
Platform Developer II (PD2) is the most challenging Salesforce developer credential. These tips help you focus on advanced Apex patterns, integration architecture, and the design principles that distinguish PD2 from entry-level developer exams.
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: What PD2 Actually Tests
- Not just Apex syntax — PD2 expects enterprise-grade design patterns: trigger frameworks, Separation of Concerns (SoC), and selector/domain/service layers.
- Integration depth — REST and SOAP callouts with Named Credentials, HttpCalloutMock, WebServiceMock, and proper error handling patterns.
- Async Apex mastery — Batch, Queueable, Schedulable, and Platform Events are tested at implementation depth, not just awareness level.
High-Weight PD2 Exam Sections to Prioritise
The top three sections account for 76% of the exam. Focus your first four weeks here.
Scenario Strategy: How to Approach PD2 Questions
PD2 questions describe a technical requirement or architectural problem and ask which pattern, mechanism, or configuration is the right solution. The correct answer always follows enterprise design principles — separation of concerns, testability, and scalability.
- For async questions: choose the mechanism based on volume and latency. Queueable = chaining + object context; Batch = millions of records; Schedulable = time-based; Platform Events = decoupled integration.
- For integration questions: REST callouts use Named Credentials and HttpCalloutMock in tests; SOAP uses WebServiceMock. Always pick the mock that matches the callout type.
- For design pattern questions: if the scenario describes multiple objects or cross-object logic, the answer involves a Service layer or Selector layer — not a trigger directly.
Advanced Apex Patterns You Must Know
PD2 questions test whether you understand why patterns exist, not just that they exist. For each pattern, know: when to use it, what problem it solves, and what the anti-pattern looks like.
- Trigger framework (handler pattern): One trigger per object, logic in handler class, no business logic in trigger itself.
- Selector / Domain / Service layers: Separation of Concerns for enterprise Apex. Know what each layer owns and why mixing them creates bulk API failures.
- HttpCalloutMock and WebServiceMock: Every integration test needs a mock. PD2 tests whether you mock correctly, not just whether tests pass.
- Platform Events and CDC: Decoupled architecture for async integration. Know when to use PE vs Queueable vs Batch.
Mock-Test Benchmark Before Booking
PD2 has a lower first-attempt pass rate than PD1. Use this minimum benchmark:
75%+ on 3 timed full mocks — only then book
Unlike PD1, scoring 70% in mocks is not sufficient for PD2 — the real exam is harder in the integration and design-pattern sections. Be conservative.
3 Concepts That Fail Most Platform Developer II (PD2) Candidates
These are not the hardest topics — they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. Apex Design Patterns — Separation of Concerns in Trigger Architecture
PD2 tests Apex design patterns: Trigger Handler pattern separates trigger logic from the trigger file. Service Layer pattern contains reusable business logic. Selector pattern centralises SOQL queries. Domain Layer validates and processes records. Candidates write all logic directly in Apex triggers — the exam expects Trigger Handler pattern at minimum, and asks which layer a specific piece of logic belongs in.
2. Asynchronous Apex: Future vs Queueable vs Batch vs Scheduled
@future: runs one asynchronous method, no chaining, no state. Queueable: like @future but supports chaining, object parameters, and monitoring. Batch: processes large data volumes in chunks (up to 50M records). Scheduled: executes on a cron-like schedule. Candidates use @future for all async operations — the exam expects Queueable when chaining is needed, Batch for large data sets, and Scheduled for recurring jobs.
3. Platform Cache — Partitioned Storage That Does Not Persist Across Deployments
Platform Cache stores computed values (formula results, complex SOQL outputs) in an in-memory cache with a defined TTL, reducing repeated computation. Org Cache is shared across all users; Session Cache is user-session-specific. Cache is NOT persistent — values are lost on deployment, maintenance, or TTL expiry. Candidates design Platform Cache as a permanent data store — the exam expects fallback logic to regenerate values on cache miss.
Frequently Asked Questions
- What is the PD2 exam format?
- The Platform Developer II (PD2) exam has 60 multiple-choice questions, a 120-minute time limit, a 65% passing score, and a $200 fee. It requires PD1 certification as a prerequisite.
- What are the highest-weight PD2 exam sections?
- Apex and the Salesforce Platform (28%), Process Automation and Logic (25%), and Debugging, Testing, and Deployment (23%) together account for 76% of the PD2 exam. Mastering these three sections is essential to pass.
- How hard is the PD2 exam compared to PD1?
- PD2 is significantly harder than PD1. It tests advanced design patterns (trigger frameworks, selector/domain/service layers), complex REST/SOAP integrations, and asynchronous Apex. Most candidates need 12–18 months of real Apex project experience after PD1 before attempting PD2.
- How should I prepare for the PD2 exam?
- Build real Apex projects using enterprise design patterns (Separation of Concerns, trigger frameworks). Practice REST and SOAP callouts with Named Credentials and HttpCalloutMock. Study Platform Events and the Streaming API. Take timed mocks — aim for 75%+ consistently before booking.
- What concepts do most Platform Developer II (PD2) candidates get wrong?
- The most commonly misunderstood topics for the Platform Developer II (PD2) exam are: (1) Apex Design Patterns — Separation of Concerns in Trigger Architecture; (2) Asynchronous Apex: Future vs Queueable vs Batch vs Scheduled; (3) Platform Cache — Partitioned Storage That Does Not Persist Across Deployments. 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 PD2 candidates fail questions about Apex Design Patterns?
- PD2 tests Apex design patterns: Trigger Handler pattern separates trigger logic from the trigger file. Service Layer pattern contains reusable business logic. Selector pattern centralises SOQL queries. Domain Layer validates and processes records. Candidates write all logic directly in Apex triggers — the exam expects Trigger Handler pattern at minimum, and asks which layer a specific piece of ...
- Why do most PD2 candidates fail questions about Asynchronous Apex: Future vs Queueable vs Batch vs S...?
- @future: runs one asynchronous method, no chaining, no state. Queueable: like @future but supports chaining, object parameters, and monitoring. Batch: processes large data volumes in chunks (up to 50M records). Scheduled: executes on a cron-like schedule. Candidates use @future for all async operations — the exam expects Queueable when chaining is needed, Batch for large data sets, and Schedule...
- Why do most PD2 candidates fail questions about Platform Cache?
- Platform Cache stores computed values (formula results, complex SOQL outputs) in an in-memory cache with a defined TTL, reducing repeated computation. Org Cache is shared across all users; Session Cache is user-session-specific. Cache is NOT persistent — values are lost on deployment, maintenance, or TTL expiry. Candidates design Platform Cache as a permanent data store — the exam expects fallb...
Related Exam Tips
Start PD2 Prep
Apply these tips with real exam-style practice:
After this exam, consider Platform Developer II or Platform App Builder next.