Lesson 3 of 22 · All lessons

Section 2 · Data Model · 15% of exam

2.2 Relationships and Customer Lifecycles

3 min read Updated Nov 19, 2026

Exam objective

Choose foundational features that make records visible to appropriate users and preserve reliable data.

Extra concept

Extra concept: Duplicate management can use matching and duplicate rules to identify likely duplicate records. These controls complement careful lead conversion but do not replace human review of ambiguous matches.

Core concepts

Data visibility and data integrity solve different problems. Visibility determines which users can see or edit a record or field. Integrity means records are accurate, complete, and consistent enough to support decisions. A user who cannot see a record has an access problem; a record with an invalid phone number or missing region has a quality problem. Salesforce provides separate tools for these needs, so identify the symptom before selecting a feature.

For integrity, consider required fields, field types, picklists, duplicate management, and validation rules. A picklist can constrain a status to approved values. A validation rule can prevent a proposal from being marked “Ready” unless a decision date is entered. The rule should express a genuine business condition, explain the correction clearly, and avoid blocking legitimate exceptions. A required field is suitable when a value must always exist; a conditional validation rule is better when the requirement depends on stage or record type.

Scenario: A service team finds Cases marked Closed without a resolution summary. If every closed Case requires a summary, a validation rule can prevent closure while the summary is blank. If only particular Case types require it, encode that condition. Test with users and record types that follow different paths. A rule that works for a single administrator may block integrations, imports, or valid bulk updates if assumptions about the data are too narrow. Visibility uses multiple layers. Organization-level controls govern who can log in and basic settings. Profiles and permission sets grant object and field permissions. Record-level sharing determines which particular records a user can access. The role hierarchy, sharing rules, teams, and manual sharing can extend record access depending on configuration. Do not use a validation rule to hide records, and do not broaden record sharing to fix a missing object permission.

When investigating a visibility complaint, ask whether the user can open the object at all, whether the record exists, and whether another user can access it. Then distinguish object permission, field-level access, and record sharing. A field that is hidden from a page layout may still be accessible through another interface if field-level security permits it. Page placement is not a security boundary.

Prefer least privilege. Grant only the access needed for the user’s work, and test with a representative standard user rather than relying on an administrator account.

Key takeaways

  • Relationships connect records so users can move from one business context to another.
  • Lead conversion is a lifecycle transition, not simply a change of label.
  • Example: A training provider receives two inquiries from different employees at the same company. Official references: https://help.salesforce.com/s/articleView?id=sales.sales_core_manage_accounts_contacts.htm&language=en_US&type=5 https://help.salesforce.com/s/articleView?id=sales.leads_def.htm&language=en_US&type=5 https://help.salesforce.com/s/articleView?id=xcloud.basics_organize_data.htm&language=en_US&type=5 https://trailhead.salesforce.com/content/learn/modules/cert-prep-salesforce-certified-associate/study-up-on-the-data-model

Check your knowledge

Answer exam-style Data Model questions with answers and explanations.

Practice Data Model
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

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

Get Complete Access