Failed Salesforce Platform Developer I twice — what I changed for the third attempt
Two fails hurt. The first time I scored 58%, needed 65%. Second time I got 62% and thought I was ready — I really wasn't. Both times I was relying too heavily on Trailhead modules and not enough on actually building things in a scratch org. That was the core problem and it took me two failures to see it clearly.
For the third attempt I built a mini app from scratch — custom objects, trigger handlers, a basic LWC component with wire adapters, and a flow that handled some data transformation. That hands-on time was worth more than probably 40 hours of reading. When you actually break things and debug them, the error messages start making sense in a way they don't when you're just reading about them.
Governor limits are heavily tested and I kept underestimating how specific the questions get. Not just knowing the limits exist but knowing what counts against which limit in what context, how to restructure code to stay within them, and the order of execution in triggers. That last one is tested probably 5-8 times in different forms depending on the exam version.
Third attempt: 72%. The process design section was easier than I expected because I'd been building flows in my scratch org. SOQL and SOSL queries were fine. Apex testing and the 75% code coverage requirement showed up in a few scenario questions that were trickier than anything in the practice materials.
72% on the third attempt is a pass and that's what matters. How much time did you spend total across all three attempts? I'm trying to budget realistically and most people who pass seem to undercount how many hours they actually put in.
The scratch org point is so accurate. I passed on my second attempt and the biggest thing was spending 30 minutes a day actually writing Apex instead of reading about it. The hands-on muscle memory carries over directly to recognizing wrong answers on the exam.
Governor limits got me on my first attempt too. I memorized the numbers — 100 SOQL queries, 150 DML statements — but I didn't understand how bulkification worked in practice. Once that clicked the limit questions became much easier to reason through.
The LWC section was harder for me than pure Apex. The lifecycle hooks and reactive properties are intuitive once you've built with them but purely abstract they're confusing. Worth spinning up even a basic LWC in a playground org just to see how data flows.
Ugh, I feel this post in my soul. I work full-time and was squeezing study sessions into lunch breaks and the hour after my kids went to bed, so I had to be ruthless about what actually moved the needle. The biggest shift for me was ditching passive reading and forcing myself to build something every single session, even if it was just a tiny trigger or a flow. Also spent a lot of time on free service provider technology based practice questions because drilling scenarios under time pressure is just different from reading documentation — it exposed gaps I didn't know I had.
Honestly the 62% to pass hurts more than 58% because you think you're close. You're not close, you're still missing something conceptual. For me it was governor limits and how bulkification actually behaves in real code, not just what Trailhead says it does. If you're a working adult, don't try to cram — consistent 45-minute focused sessions beat three-hour weekend marathons where you're too tired to retain anything.
This hits home. I struggled with the same thing — I'd read the explanation for the right answer and move on, never stopping to really understand why the wrong ones were wrong. That's where the actual learning happens. Once I started treating every incorrect option like a mini-lesson, asking myself what scenario would make that answer correct or what concept it was trying to trick me on, my retention just clicked into place.
For the SP specifically, the distractor answers are usually wrong in very specific ways, and they repeat those patterns. If you've internalized the reasoning behind the errors, you start recognizing the tricks before you even finish reading the question. Flashcards for right answers didn't help me much. Building a little notes doc of "why wrong answer B is wrong on questions like this" is what actually moved my score.