Configuration & setup
⏱ ~3-min readAceMark Guide
What this topic is really about
Marking a field required ON the page layout assigned to that profile applies the requirement only for users on that layout. Field-level required applies globally to all profiles. Validation rules work but are noisier.
A validation rule evaluates a formula on save and blocks the record with an error if the criteria are not met, enforcing data quality. Workflow rules and approval processes automate downstream actions, and assignment rules route leads/cases to owners.
See the mechanism
Marking a field required ON the page layout assigned to that profile applies the requirement only for users on that layout. A diagram for this topic isn't available yet — the worked example below walks the same reasoning step by step.
An exam-style question, fully explained
An admin needs a custom field required ONLY for users with a specific profile. Best approach?
- Identify what the question tests: An admin needs a custom field required ONLY for users with a specific profile..
- Marking a field required ON the page layout assigned to that profile applies the requirement only for users on that layout.
- Field-level required applies globally to all profiles.
- Validation rules work but are noisier.
- FLS controls visibility/editability.
Traps the examiner sets
- Read each option carefully — distractors on Configuration & setup are designed to look plausible.
- Re-check the exact wording of the question stem before committing to an answer.
- Watch the qualifiers ("always", "only", "except") that flip a correct-looking option.
Test your recall
Answer each from memory — you'll see instantly whether you're right and why.
Run a focused 10-question mini-mock on Configuration & setup and see it stick.
Practice more of this topic →