Checklist progress
0/282Learned
Platform Administrator
Study Checklist
Checklist progress
0/282Learned
Describe the standard object architecture and relationship model
0/11
Explain how to create, delete, and customize fields and page layouts on standard and custom objects, and know the implications of deleting fields
0/20
Custom field creation on standard and custom objects
Learn this conceptPicklist and multi-select field configuration
Learn this conceptControlling fields for picklist dependencies
Learn this conceptPicklist value deactivation versus deletion
Learn this conceptAuto-number field configuration
Learn this conceptRoll-up summary relationship rules
Learn this conceptSupported roll-up aggregate functions
Learn this conceptLookup filters on relationship fields
Learn this conceptLookup versus master-detail field conversion
Learn this conceptPage layout sections and field placement
Learn this conceptPage-layout required versus field-level security
Learn this conceptCustom field deletion and recovery
Learn this conceptDeleting fields used by roll-up summaries
Learn this conceptDeleting fields used by cross-object formulas
Learn this conceptDeleting fields used in picklist dependencies
Learn this conceptDeleting lookup and master-detail fields
Learn this conceptGiven a scenario, determine how to create and assign page layouts, visibility on Lightning page layouts, record types, and business processes for custom and standard objects
0/12
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Administrator studiers. 593 members and growing.
Page layouts and field-level security both affect whether a user sees a field and whether they must fill it in, but they work at different layers. Field-level security decides whether a user can see or change a field value anywhere in the app, while a page layout arranges the record page and can mark a field required, read-only, or hidden on that page. When those settings conflict, field-level security wins.