A sales team uses the standard Salesforce data model. They want to allow users to attach multiple contacts to a single opportunity, but they also want to track the role each contact plays (e.g., 'Decision Maker', 'Influencer'). What is the recommended way to achieve this?

Create a custom multi-select picklist on Opportunity to store contact roles

Use the standard OpportunityContactRole object

Create a custom lookup field on Contact to Opportunity

Use the standard CampaignMember object

A company is using Salesforce to track both B2B and B2C sales. They have a single Account object, but they need to differentiate between business accounts and individual consumers. They also need to track the same person as both a Contact and a Lead. What is the best approach?

Use a single Account record type and a checkbox to indicate business or consumer

Create two custom objects for BusinessAccount and ConsumerAccount

Use the standard Person Account feature for consumer accounts and standard Account for business accounts

Use record types on Account to differentiate business and consumer accounts, and use standard Lead and Contact objects with conversion

What is the purpose of record types on standard objects like Account or Case?

To create a new object with a different set of fields.

To restrict which users can view records.

To define different page layouts and picklist values for different business processes.

To store different types of data in the same record.

An administrator is setting up a new Salesforce org. They need to ensure that when a user creates an Opportunity, the Stage field defaults to 'Prospecting' and the Amount field is required. They also want to prevent users from changing the Stage to 'Closed Won' if the Amount is blank. What is the best way to achieve this?

Use a record type with a default Stage and a page layout with Amount required

Use a flow to set Stage to 'Prospecting' and a validation rule to require Amount

Set the default value of Stage to 'Prospecting' via the field's default value, make Amount required via field-level security, and add a validation rule to block 'Closed Won' without Amount

Use a workflow rule to set Stage to 'Prospecting' and a validation rule to require Amount

SalesforceCertified Administrator

Domain 4Objective 1

Describe the Standard Object Architecture and Relationship Model. PLATFORM-ADMINISTRATOR Practice Questions (Page 1)

Part of the STANDARD AND CUSTOM OBJECTS domain, which accounts for 15% of the PLATFORM-ADMINISTRATOR exam.

17questions here

4free pages

4concepts

15%of the exam

Questions 1–5

1foundation · easy
In the standard Salesforce data model, which standard object is the parent in a master-detail relationship with Opportunity?
Select an answer first
2application · medium
A sales team uses the standard Salesforce data model. They want to allow users to attach multiple contacts to a single opportunity, but they also want to track the role each contact plays (e.g., 'Decision Maker', 'Influencer'). What is the recommended way to achieve this?
Select an answer first
3expert · hard
A company is using Salesforce to track both B2B and B2C sales. They have a single Account object, but they need to differentiate between business accounts and individual consumers. They also need to track the same person as both a Contact and a Lead. What is the best approach?
Select an answer first
4foundation · easy
What is the purpose of record types on standard objects like Account or Case?
Select an answer first
5expert · hard
An administrator is setting up a new Salesforce org. They need to ensure that when a user creates an Opportunity, the Stage field defaults to 'Prospecting' and the Amount field is required. They also want to prevent users from changing the Stage to 'Closed Won' if the Amount is blank. What is the best way to achieve this?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PLATFORM-ADMINISTRATOR

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Salesforce. “PLATFORM-ADMINISTRATOR” is a trademark of its owner, used for identification only.

Describe the Standard Object Architecture and Relationship Model. PLATFORM-ADMINISTRATOR Practice Questions (Page 1)

Questions 1–5

In the standard Salesforce data model, which standard object is the parent in a master-detail relationship with Opportunity?

A sales team uses the standard Salesforce data model. They want to allow users to attach multiple contacts to a single opportunity, but they also want to track the role each contact plays (e.g., 'Decision Maker', 'Influencer'). What is the recommended way to achieve this?

A company is using Salesforce to track both B2B and B2C sales. They have a single Account object, but they need to differentiate between business accounts and individual consumers. They also need to track the same person as both a Contact and a Lead. What is the best approach?

What is the purpose of record types on standard objects like Account or Case?

Keep studying — STANDARD AND CUSTOM OBJECTS