SF-Admin Sales and Marketing Applications Practice Question
A sales manager needs to see the total number of open opportunities and the sum of their 'Amount' fields on the Account record. Which TWO features should the administrator use to achieve this?
⚠ Common exam trap
Candidates often suggest Lookup relationships. However, roll-up summary fields require a Master-Detail relationship to calculate values from child records, making the Lookup relationship an incorrect choice for this specific requirement.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Roll-up Summary Field
Roll-up summary fields and Master-Detail relationships are required here. A Master-Detail relationship allows parent-child data aggregation, while the roll-up summary field performs the actual calculation of record counts and sums. This combination is essential for providing real-time visibility into account-level performance metrics, which is critical for sales managers to assess account health and prioritize high-value activities effectively across their diverse portfolio of client relationships.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Roll-up Summary Field
Why this is correct
Roll-up summary fields are specifically designed to calculate values from related records, such as count or sum, and display them on the parent object. This is the only declarative method to aggregate numeric data from multiple child records without requiring custom code or third-party automation tools.
- ✓
Master-Detail Relationship
Why this is correct
Master-Detail relationships enable roll-up summary fields by creating a parent-child link where the child record's lifecycle is tied to the parent. This architectural dependency is a strict prerequisite for the platform to maintain data integrity when performing automated aggregations on the parent account record.
- ✗
Lookup Relationship
Why it's wrong here
Lookup relationships do not support roll-up summary fields because they are loosely coupled. Records in a lookup relationship do not have the same dependency as master-detail, so the platform cannot guarantee the accuracy of aggregated data, necessitating the use of alternative methods like Flow for calculations.
- ✗
Quick Action
Why it's wrong here
Quick actions allow users to create or update records but do not perform calculations or data aggregations. While they enhance user experience by streamlining data entry, they have no functional capability to perform summary operations across related lists or calculate sums from child opportunity records.
- ✗
Validation Rule
Why it's wrong here
Validation rules are used to enforce data quality by preventing records from being saved if they do not meet specific criteria. They do not have the ability to aggregate data or perform mathematical calculations across related records, making them irrelevant for the requirement of calculating account-wide totals.
About these practice questions
Courseiva writes every SF-Admin question from scratch — 202 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Admin practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Admin exam.