SF-Admin Configuration and Setup Practice Question
Which Salesforce tool should an administrator use to view a history of all configuration changes made in the environment?
⚠ Common exam trap
Candidates frequently confuse the Setup Audit Trail with Field History Tracking. Audit Trail tracks backend configuration changes, while Field History tracks specific record data changes on an object.
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
✓
Setup Audit Trail
The Setup Audit Trail tracks the recent setup changes that you and other administrators have made to your organization. This is a critical tool for troubleshooting, auditing, and maintaining compliance. It logs details like who made the change, when it occurred, and what specifically was modified, providing a clear timeline of administrative activity within the Salesforce org.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Debug Log
Why it's wrong here
Debug Logs are used to track specific execution paths, database queries, and code performance for troubleshooting Apex, processes, or flows. They are not intended for tracking configuration changes made in the Setup menu. They provide granular technical insight rather than an administrative audit trail of organizational configuration modifications.
- ✓
Setup Audit Trail
Why this is correct
The Setup Audit Trail records the last 6 months of configuration changes made to the organization. It is the primary tool for administrators to review administrative actions, such as creating fields, modifying profiles, or changing security settings, making it the definitive source for auditing setup-related configuration changes in Salesforce.
- ✗
Login History
Why it's wrong here
The Login History feature tracks information about user login attempts, including status, source IP, and authentication method. It does not record any configuration changes made by administrators within the setup interface. It is purely focused on user access and authentication security metrics rather than administrative metadata changes.
- ✗
Field History Tracking
Why it's wrong here
Field History Tracking is used to monitor changes to specific data values within records on an object. It does not track changes to the configuration of the Salesforce instance itself, such as adding a new custom field or changing a security profile. It is a data-level, not configuration-level, tracking mechanism.
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.