SF-Admin Sales and Marketing Applications Practice Question
Which feature allows an administrator to track changes to the 'Amount' field on an Opportunity over time?
⚠ Common exam trap
Candidates often confuse Field History Tracking with Setup Audit Trail. While Audit Trail tracks configuration changes, it does not track data value changes on individual records like Opportunities.
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
✓
Field History Tracking
Field History Tracking is the standard tool for auditing changes to specific fields. By enabling it, the administrator can see the old value, new value, date, and user who performed the change. This is essential for sales operations to identify who changed deal values, which helps in auditing forecasting accuracy and identifying potential training needs for sales representatives handling sensitive opportunity data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Field History Tracking
Why this is correct
Field history tracking captures every change made to a field, including the old and new values. This is an essential administrative tool for maintaining data transparency and accountability, allowing managers to see exactly how and when opportunity data has been modified throughout the deal's lifecycle.
- ✗
Roll-up Summary
Why it's wrong here
Roll-up summary fields calculate the current total of child records. They do not track the history or audit trail of changes made to fields. Using them to track changes would provide no visibility into previous values or the timeline of modifications, making them useless for audit requirements.
- ✗
Workflow Rule
Why it's wrong here
Workflow rules are used for automation, not auditing. They can trigger actions based on field changes, but they do not maintain a historical record of what those changes were, meaning they cannot provide the audit trail necessary for tracking modifications to the amount field over time.
- ✗
Validation Rule
Why it's wrong here
Validation rules are used to restrict data input based on business criteria. They do not record or display a history of changes. They simply evaluate the current data during the save process and have no memory of past values, rendering them ineffective for tracking historical field modifications.
About these practice questions
This SF-Admin question is part of Courseiva's 202-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.