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
Apex collection variable declaration
Learn this conceptApex constants and the final keyword
Learn this conceptApex method declaration and argument passing
Learn this conceptAccess modifiers for Apex classes and members
Learn this conceptStatic versus instance members in Apex
Learn this conceptApex properties versus member variables
Learn this conceptApex interfaces and implementing classes
Learn this conceptVirtual, abstract, and override class modifiers
Learn this conceptSharing keywords on Apex class declarations
Learn this conceptTransient members and Apex serialization
Learn this conceptGiven 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
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. 593 members and growing.
An Apex interface is like a class whose methods have signatures but empty bodies, so it names a contract without supplying an implementation. Another class implements the interface by writing a body for every method on that contract, which separates the declaration of a method from any one specific implementation. That lets you keep different behavior behind one type, for example customer and employee purchase orders that both expose discount but return different amounts.