SF-Admin Object Manager and Lightning App Builder Practice Question
An administrator needs to track the history of changes made to a custom field on a custom object. Which feature should they enable to ensure this is logged?
⚠ Common exam trap
Candidates often think enabling 'Audit Trail' is the correct answer, but the Setup Audit Trail tracks configuration changes, not record-level field data changes on custom objects.
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
✓
Enable 'Track Field History' on the object and select the specific field.
Field History Tracking is the standard Salesforce feature used to monitor changes to specific fields. Enabling this allows users to see an audit trail in the 'History' related list, which captures the date, time, user, and old/new values. This is a vital component for organizational compliance, security auditing, and troubleshooting issues where data values might have been altered incorrectly by users or automated processes over time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable 'Track Field History' on the object and select the specific field.
Why this is correct
Field history tracking must be enabled at the object level first, followed by selecting the individual fields to be monitored. Once configured, Salesforce automatically logs changes to the 'History' related list. This provides a clear, documented audit trail that is accessible to authorized users for reporting and review purposes.
- ✗
Add the 'Field Audit Trail' permission set to the user profile.
Why it's wrong here
Field Audit Trail is an enterprise-grade feature used for long-term retention of historical data, which requires a specific add-on license. It is not the standard mechanism for tracking simple field changes. Enabling the standard field history tracking is sufficient for most business needs and does not require additional licenses.
- ✗
Configure an Apex trigger to log changes to a custom object.
Why it's wrong here
While an Apex trigger can log changes, it is not a declarative solution. Salesforce provides built-in, no-code functionality for this purpose via Field History Tracking. Using custom code for simple auditing increases technical debt, requires maintenance, and is unnecessary when the platform already provides this native, robust, and supported feature.
- ✗
Create a new Report Type on the custom object.
Why it's wrong here
Report types define which records and fields are available for reporting, but they do not actively track or log changes made to data. You cannot report on historical field changes unless you have first enabled Field History Tracking to capture that data into the system's underlying audit tables.
About these practice questions
One of 202 original SF-Admin practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.