Checklist progress
0/194Learned
Platform Developer
Study Checklist
Checklist progress
0/194Learned
Identify the capabilities of the declarative process automation features.
0/8
Understand how to declare variables, constants, methods, modifiers, Apex interfaces, and the appropriate use cases for each.
0/15
Given a scenario, assess how Apex control flow statements will execute and when to apply different control flow statements.
0/8
Given a scenario, write SOSL, SOQL, and DML statements in Apex, and assess what they will return.
0/18
Given a scenario, follow best practices to write Apex classes and triggers.
0/6
Apex trigger definition syntax
Learn this conceptBefore versus after Apex triggers
Learn this conceptTrigger context variable availability
Learn this conceptCalling a class method from a trigger
Learn this conceptBulk-safe Apex trigger and class design
Learn this conceptGiven a scenario, understand governor limits and their implications on Apex transactions.
0/5
Describe the relationship between Apex transactions, the save order of execution, and the potential for recursion and/or cascading.
0/10
Implement exception handling in Apex, including custom exceptions as needed.
0/7
Given a scenario, use declarative functionality and Apex together to automate business logic.
0/7
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Developer studiers.
Apex often runs a trigger or class against a whole batch of records at once, not only the one record a person saved in the user interface. Bulk-safe design means looping over that entire set and issuing Salesforce queries (SOQL) and inserts, updates, or deletes (DML) against collections instead of handling records one at a time. That pattern exists because the platform caps how many queries and database writes a transaction may perform, and a per-record loop hits those caps as soon as the batch is large.