Lesson 8 of 29 · All lessons
Salesforce Platform Administrator
0 of 29 complete
1ADM-201 Exam Overview
  1. 1.1ADM-201 Exam Overview
2Configuration and Setup15%
  1. 2.1Company settings, fiscal year, business hours, currency, and defaults
  2. 2.2Declarative user interface configuration
  3. 2.3User setup, licensing, and lifecycle
  4. 2.4Organization security and identity controls
  5. 2.5Sharing model, record access, and folders
  6. 2.6Profiles, permission sets, groups, and muting
3Object Manager and Lightning App Builder15%
  1. 3.1Objects, schema, and relationship architecture
  2. 3.2Fields, formulas, and field dependencies
  3. 3.3Page layouts, Lightning pages, record types, and actions
4Sales and Marketing Applications10%
  1. 4.1Leads, opportunities, sales processes, and Path
  2. 4.2Campaigns, campaign members, and lead assignment
  3. 4.3Sales productivity, scoring, forecasting, and territories
5Service and Support Applications10%
  1. 5.1Case management, queues, and case assignment
  2. 5.2Support processes, auto-response, escalation, and Einstein for Service
6Productivity and Collaboration10%
  1. 6.1Tasks, events, and activity management
  2. 6.2Chatter, groups, and internal or external collaboration
  3. 6.3Salesforce mobile app configuration and user experience
  4. 6.4AppExchange, packages, AgentExchange, and Flow awareness
7Data and Analytics Management17%
  1. 7.1Importing, updating, transferring, deleting, exporting, and backing up data
  2. 7.2Matching rules, duplicate rules, and validation rules
  3. 7.3Reports and report types
  4. 7.4Sharing, folders, and report visibility
  5. 7.5Dashboards, components, filters, subscriptions, refresh, and licensing
8Automation15%
  1. 8.1Selecting automation tools for a business scenario
  2. 8.2Flow capabilities, types, configuration, and order of execution
  3. 8.3Approval processes, criteria, approvers, and outcomes
9Agentforce8%
  1. 9.1Agentforce capabilities, use cases, security, and permissions
  2. 9.2Agent Builder, prompts, instructions, testing, and conversation preview

Section 3 · Object Manager and Lightning App Builder · 15% of exam

3.1 Objects, schema, and relationship architecture

2 min read Updated Nov 13, 2026

Exam objective

Describe standard and custom objects, parent-child architecture, relationship models, record types, and Schema Builder.

Standard objects such as Account, Contact, Lead, Opportunity, and Case support common CRM processes. A custom object models an organization-specific entity when standard objects do not represent the business data appropriately. Good data modeling starts by identifying the entities, their lifecycle, and how users need to report on them. Lookup relationships connect records while allowing more independence. Master-detail creates a tighter parent-child dependency, including behaviors such as inherited ownership and sharing and support for roll-up summaries. A junction object connects two objects in a many-to-many pattern, commonly through two master-detail relationships. These choices affect requiredness, deletion, access, and reporting.

Schema Builder gives a visual view of objects and relationships to help administrators understand the model. Record types support different business processes, picklist values, and page layouts for different audiences; they do not create separate objects or security boundaries.

Additional concepts

Relationship patterns

Select a relationship from the required independence, ownership, deletion, roll-up, and access behavior. A lookup allows a looser association; master-detail creates a stronger dependency on the master; a junction object represents a many-to-many association.

RelationshipTypical useDesign question
LookupRelated records can be more independentCan the child exist without its parent?
Master-detailChild depends on a masterShould ownership and sharing follow the master?
JunctionMany-to-many associationMust one record connect to records on two objects?

Record types are not separate objects

Record types can support different processes, picklist values, and layouts for audiences using the same object. They do not create a separate data object or a security boundary. Schema Builder helps visualize object relationships; it does not replace planning for access or lifecycle behavior.

A company tracks installed equipment associated with customers and service cases. Model equipment as a custom object and choose relationships based on whether equipment must exist independently and how its access should behave.

Decide relationship behavior from ownership, deletion, sharing, and reporting requirements—not just from the labels “parent” and “child.”

Key takeaways

  • Standard objects fit common CRM entities; custom objects model organization-specific data.
  • Lookup and master-detail relationships have different dependency and access behavior.
  • Junction objects model many-to-many relationships; record types model different processes on one object.

Check your knowledge

Answer exam-style Object Manager and Lightning App Builder questions with answers and explanations.

Practice Object Manager and Lightning App Builder
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator simulator: same number of questions, same time limit.

Get Complete Access