Study guide

4.3 Lookup, Master-Detail, and Junction Relationships

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

4.3 Lookup, Master-Detail, and Junction Relationships

Key Takeaways Explain This Topic AI

Lookup relationships connect records while preserving more independence between parent and child records.

Master-detail relationships tightly bind detail records to the master through ownership, sharing, deletion behavior, and native roll-up summary capability.

Junction objects model many-to-many relationships by placing two relationships, commonly master-detail relationships, on an intermediate object.

Relationship choices affect security, reporting, automation, deletion behavior, and future conversion options.

Last updated: May 2026

Relationship Decisions

Relationships make the Salesforce data model useful. Without relationships, an admin only has separate lists of records. With relationships, Accounts can show Contacts, Cases can point to Assets, custom Projects can contain Milestones, and reports can answer questions across business processes. The main admin decision is whether the relationship should be loose, tight, or many-to-many.

A lookup relationship links one record to another while allowing the child record to retain more independence. The child can usually have its own owner, sharing, and lifecycle. Lookup fields can be optional or required, depending on configuration and business rules. Lookup is a strong fit when the child can exist without the parent or when the parent should not control the child record's access and deletion behavior.

A master-detail relationship is more tightly coupled. The detail record depends on the master record. Detail records do not have an independent owner in the same way as standalone records, and access to detail records is controlled by the master. Deleting the master deletes related detail records. Native roll-up summary fields become available on the master because Salesforce can trust that tight parent-child structure.

  • Design question Lookup leaning Master-detail leaning
  • Can the child exist without the parent? Yes No
  • Should the child have independent ownership? Yes No
  • Should parent deletion delete children? Usually no Yes
  • Need native roll-up summary fields? Not natively Yes
  • Should child sharing follow the parent? Not necessarily Yes

Because relationship type affects security and data lifecycle, it is not just a reporting choice. Suppose a custom Expense record belongs to a Project. If expenses should only be visible to users who can see the project, and deleting the project should remove its expenses, master-detail may fit. If expenses can be reassigned, owned by finance, or retained after a project is archived, lookup may be safer.

Lookup filters add another layer. A lookup filter limits which parent records are valid choices. For example, a Case lookup to Asset can be filtered so users select only assets related to the Case account. Filters improve data quality and user experience, but they do not replace object permissions or sharing. A user still needs access to the target records and fields.

Junction objects model many-to-many relationships. A common pattern is Student, Course, and Enrollment. A student can enroll in many courses, and a course can have many students. The Enrollment object sits between them and stores relationship-specific fields such as enrollment date, status, grade, or attendance. Without the junction object, those relationship details have no clean home.

  • Many-to-many model Role
  • Student One side of the relationship
  • Course Other side of the relationship
  • Enrollment Junction record connecting one student to one course
  • Enrollment Status Field on the junction, because it describes the connection

A junction object often uses two master-detail relationships, especially when the connection should be tightly dependent on both parent records. In some designs, lookup relationships may be chosen instead if the junction record needs more independence. The admin should evaluate deletion behavior, ownership, sharing, reporting, roll-ups, and whether the connection record has its own lifecycle.

Relationship conversion is another exam area. A lookup may be convertible to master-detail only when the data and configuration meet the requirements, such as existing child records having parent values. A master-detail relationship may have dependencies such as roll-up summary fields that must be addressed before conversion. The safest admin practice is to decide relationship type carefully before loading production data.

Relationships also affect reporting. Standard and custom report types expose related records based on relationship paths. If executives need Projects with or without Milestones, the report type and relationship design must support that question. A master-detail relationship can make roll-ups easy, but a lookup relationship may be better when optional related records still need to appear in reports.

Automation uses relationships heavily. Flow can read parent fields, update related records, or enforce rules across records. However, automation should not be used to hide a poor relationship choice unless there is a clear reason. If every save requires complex flow logic to simulate ownership, roll-ups, or cascade behavior, the relationship model may need to be revisited.

A practical relationship checklist:

Name the parent and child records in plain business language.

Decide whether the child can exist without the parent.

Decide who owns the child and who should see it.

Decide what should happen when the parent is deleted.

Identify roll-up, report, and automation needs.

Test sample records with realistic profiles and sharing.

Document why lookup or master-detail was selected.

The common trap is choosing master-detail only because a roll-up is wanted. Roll-ups are valuable, but they are not the only requirement. If the child needs independent access, ownership, or survival after parent deletion, forcing master-detail can create operational problems. Conversely, choosing lookup for everything can lead to unnecessary automation when the business truly has a dependent detail record.