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
Given 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
Apex try, catch, and finally execution
Learn this conceptCatching specific versus generic Exception
Learn this conceptDML exception handling in try-catch
Learn this conceptUnhandled exception effects on the transaction
Learn this conceptTrigger addError versus thrown exceptions
Learn this conceptGiven 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 provides built-in exception types that the runtime throws when execution hits an error, such as a failed DML statement, a bad list index, a null dereference, or a SOQL result assigned to the wrong kind of variable. You catch those types in try-catch blocks so you can read the error instead of leaving it unhandled. Use a specific type when you know what can fail; use the generic Exception type when you need to catch whatever was thrown.