Lesson 5 of 17 · All lessons

Section 3 · Data Modeling and Management · 20% of exam

3.1 Build a Data Model and Select Relationship Types

4 min read Updated Nov 19, 2026

Exam objective

Given a scenario, determine an appropriate Salesforce data model and explain how relationship types affect access, user interface, and reporting.

A Salesforce data model describes the objects, fields, relationships, and record lifecycles that represent a business. Start from nouns and business events, then identify what has its own identity, ownership, permissions, and reporting needs. Standard objects are usually preferable when they already represent a concept such as Account, Contact, Case, or Opportunity. A custom object is appropriate for a distinct business entity with its own fields, records, lifecycle, and relationships. Avoid creating duplicate custom objects for concepts that standard objects already cover. A lookup relationship links records while keeping them comparatively independent. The child can generally exist without a parent, and the relationship does not inherit the parent’s sharing in the same way as master-detail. Use a lookup when the relationship is optional, the child needs independent ownership or sharing, or the parent-child lifecycle should remain separate. Consider whether the lookup should be required and whether deletion behavior matches retention needs. A master-detail relationship makes a child dependent on a parent. The child inherits record access from the master and is typically controlled through it. The parent can support roll-up summary fields over its detail records. This is useful for a genuine dependent component, such as a line item belonging to a transaction, but it is not merely a convenient way to create a related list. Changing an existing relationship to master-detail can be constrained by existing data, ownership, and field values. Plan and test the conversion carefully.

Many-to-many relationships commonly use a junction object with two master-detail relationships. For example, a custom Enrollment object can connect Students and Courses so each student can take many courses and each course can have many students. The junction object represents the association itself and may hold attributes such as enrollment date or status. Relationships also influence related lists, navigation, lookup filters, reports, deletion, and access calculations. Validate the model with representative records and reporting questions before implementing it. Applied scenario: A training organization needs courses, learners, and enrollments. Course and learner records have independent owners and lifecycles, while an enrollment is meaningful only for one learner and one course and must inherit controlled access. Model Course and Learner as parent objects and Enrollment as a junction object. Place enrollment-specific attributes on Enrollment, not on either parent. Confirm that the two master-detail relationships and resulting access model are suitable, then prototype reports that show learners by course and enrollment status. If enrollment must survive deletion of a parent, rethink the relationship or deletion policy before committing to this design. Design and risk review: A common modeling error is choosing master-detail solely to obtain roll-up summaries. Its access inheritance and lifecycle coupling can be inappropriate. Another is representing a many-to-many relationship with a single lookup, which forces duplication or loses associations. Check object limits, relationship limits, deletion rules, ownership needs, reporting paths, and whether users need independent sharing. The “right” model is the simplest model that preserves business meaning and supports expected access and reporting. Salesforce Certified Platform App Builder | SU ·26 guide alignment 8 Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.

Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.

Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.

Key takeaways

  • Given a scenario, determine an appropriate Salesforce data model and explain how relationship types affect access, user interface, and reporting
  • Choose the platform feature that fits the requirement, data, access, and operating context.
  • Test realistic users, exceptions, dependencies, and lifecycle effects before release.
  • Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/data_modeling

Check your knowledge

Answer exam-style Data Modeling and Management questions with answers and explanations.

Practice Data Modeling and Management
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Platform App Builder simulator: same number of questions, same time limit.

Get Complete Access