Checklist progress
0/194Learned
Platform Developer
Study Checklist
Checklist progress
0/194Learned
Given a scenario, prevent user interface and data access security vulnerabilities.
0/11
CRUD and FLS enforcement in Apex
Learn this conceptwith sharing versus without sharing on UI Apex
Learn this conceptLightning Data Service versus Apex for data access security
Learn this conceptVisualforce standard versus custom controller data access
Learn this conceptCRUD and FLS checks in Visualforce expressions
Learn this conceptSOQL injection prevention in dynamic queries
Learn this conceptVisualforce output encoding against XSS
Learn this conceptLightning component XSS and Locker protections
Learn this conceptCross-site request forgery protections in Visualforce and Lightning
Learn this conceptInsecure direct object references in UI controllers
Learn this conceptFlow system context and data access risks
Learn this conceptGiven a scenario, display and use custom user interface components, including Lightning components, Flow, and Visualforce.
0/15
Describe the use cases and best practices for Lightning Web Components, including the framework, benefits, and events.
0/13
Given a scenario, implement Apex to work with various types of page components, including Lightning components, Flow, and Agentforce.
0/5
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Developer studiers.
Authorization and access control exist so users can use only the resources they are permitted to use. Insecure direct object reference is a named authorization vulnerability in that family. On the Lightning Platform, UI controllers load Salesforce records for a page or component: standard controllers enforce the current user's object permissions and sharing, while custom Apex controllers must enforce sharing and user-mode data access or they can return records the logged-in user is not allowed to see.