Section 3 · Object Manager and Lightning App Builder · 15% of exam
3.1 Objects, schema, and relationship architecture
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.
| Relationship | Typical use | Design question |
|---|---|---|
| Lookup | Related records can be more independent | Can the child exist without its parent? |
| Master-detail | Child depends on a master | Should ownership and sharing follow the master? |
| Junction | Many-to-many association | Must 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.
