SF-Admin Object Manager and Lightning App Builder Practice Question
A sales manager wants to restrict users from editing the 'Close Date' field on Opportunities after the stage is set to 'Closed Won'. Which tool is the most efficient configuration solution to achieve this without using Apex code?
⚠ Common exam trap
Many candidates mistakenly choose approval processes or page layout read-only settings instead of validation rules when trying to restrict field edits conditionally.
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
✓
Create a Validation Rule using ISCHANGED and PRIORVALUE functions.
Validation Rules are the most appropriate declarative tool for enforcing data integrity based on field-level conditions. By checking if the current stage is 'Closed Won' and comparing the record's prior value to its current value, an administrator can prevent changes to historical data. This approach is superior to page layouts or permission sets, as it enforces the business logic at the database level regardless of the user's interface.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a Page Layout with the field set to Read-Only.
Why it's wrong here
Page layouts only control visibility and editability for a user's entire session and cannot dynamically change based on record field values. This solution would make the field read-only for all opportunities, even those in earlier stages where editing is required to update pipeline forecasts correctly.
- ✗
Assign a Permission Set with Read-Only access to the field.
Why it's wrong here
Permission sets apply to profiles and users globally and lack the conditional logic required to evaluate the Stage field. Using this method would permanently remove edit access for the user, preventing them from updating the Close Date even when the opportunity is in an active, non-closed stage.
- ✓
Create a Validation Rule using ISCHANGED and PRIORVALUE functions.
Why this is correct
Validation rules evaluate record data upon saving. By using ISCHANGED(CloseDate) and checking if the record was already closed, the system can block the save operation specifically when the business condition is met. This ensures data integrity without impacting the user interface for open, editable opportunities.
- ✗
Configure a Field-Level Security setting on the Profile.
Why it's wrong here
Field-Level Security is a static configuration that defines whether a user can see or edit a field globally across the entire object. It does not possess the capability to perform conditional checks against other fields like Stage, making it an ineffective tool for this specific business requirement.
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.