Praxis Academy
Home › Platform Foundations › Data Model

Platform Foundations practice questions: Data Model

Data Model is 25% of the Salesforce Certified Platform Foundations exam. It covers objects, fields and relationships. Try these 5 free questions, then open each answer to see why every option is right or wrong.

01

A field must be mandatory only when a lead reaches one specific stage. What is the right way to build this?

  1. Make the field required at the field level
  2. Validation Rule
  3. Make the field required on the page layout
Show answer

Answer: B

A. Make the field required at the field levelIncorrect. Field-level required applies to every record in every stage, API saves included.
B. Validation Rule ✓Correct. A validation rule can look at the lead's stage and stop the save only when the field is blank at that stage.
C. Make the field required on the page layoutIncorrect. A page-layout requirement covers every record that uses the layout, whatever its stage.

Why: A validation rule can block the save only when the lead is in the stage in question and the field is empty. Marking the field required on the page layout, or at the field level, would enforce it no matter what stage the lead is in.

02

Several departments each need to give their users extra access specific to that department. What should be used?

  1. Sharing Set
  2. Permission Set
  3. Profile
Show answer

Answer: B

A. Sharing SetIncorrect. Sharing sets give Experience Cloud users record access; they do not grant permissions to internal users.
B. Permission Set ✓Correct. Permission sets add permissions on top of a user's profile, so each department can get its own extra access.
C. ProfileIncorrect. A user holds only one profile, and building profiles per department is far less flexible than permission sets.

Why: A profile sets each user's baseline access, usually tied to a job function. Permission sets layer extra permissions on top of it, so each department can receive its own additional access without cloning profiles for every variation.

03

Which kind of relationship connects Accounts and Contacts?

  1. Self Relationship
  2. Master Detail
  3. Lookup
Show answer

Answer: C

A. Self RelationshipIncorrect. A self relationship points an object at itself, for example an Account to its parent Account.
B. Master DetailIncorrect. Contacts can exist without an account (private contacts), so the relationship cannot be master-detail.
C. Lookup ✓Correct. Contact links to Account through a lookup, so a contact does not need an account.

Why: An account may have many contacts, yet a contact can also exist with no account at all (often called an orphan or private contact), which is why the link is a lookup.

04

A software firm has qualified a lead and wants to convert it into a company record, a person record and, if needed, a deal record. Which two standard objects result from every lead conversion? (Choose 2)

  1. Account
  2. Contact
  3. Opportunity
  4. Lead
Show answer

Answer: A, B

A. Account ✓Correct. Converting a lead always creates or matches an Account.
B. Contact ✓Correct. Converting a lead always creates or matches a Contact.
C. OpportunityIncorrect. Creating an Opportunity during conversion is optional.
D. LeadIncorrect. The Lead is the source being converted, not a new record that gets created.

Why: Every lead conversion creates an Account and a Contact, or matches them to existing ones. Creating an Opportunity is optional. The Lead is the record being converted and is simply flagged as converted afterward; no new Lead is created.

05

A sneaker company has locked account access down to the most restrictive baseline. The admin now must automatically give one group of users access to accounts owned by a different group. Which feature creates automatic exceptions to the baseline?

  1. Sharing Rules
  2. Permission Sets
  3. Organization-Wide Defaults
  4. Field-Level Security
Show answer

Answer: A

A. Sharing Rules ✓Correct. Sharing rules automatically extend access past the org-wide defaults for defined groups.
B. Permission SetsIncorrect. Permission sets grant object and field permissions, not record sharing between groups.
C. Organization-Wide DefaultsIncorrect. Org-wide defaults define the baseline and do not create exceptions.
D. Field-Level SecurityIncorrect. Field-level security governs fields, not records.

Why: Sharing Rules automatically open record access beyond the organization-wide sharing settings for defined sets of users. Organization-Wide Defaults establish the baseline but carve out no exceptions, Field-Level Security governs individual fields rather than records, and Permission Sets grant object and field permissions without sharing records between groups.

Find out if you're ready to pass

Take the free Platform Foundations diagnostic: 20 questions, no account needed. Then unlock all 80 questions, full practice exams and the study guide.

Start the free diagnosticSee plans

Other sections of this exam