SF-Admin Configuration and Setup Practice Question
The administrator at Cloud Kicks has been asked to ensure that when a user creates a new case, the 'Priority' field defaults to 'Medium' but can still be changed to 'High' or 'Low'. The administrator wants to minimize manual data entry and ensure consistency. What is the most efficient way to configure this?
⚠ Common exam trap
The trap here is overcomplicating the solution with automation when a simple field default achieves the same result without interfering with user edits.
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
✓
Set the default value of the Priority picklist field to 'Medium' in the field definition.
Setting a default value on the picklist field is the most efficient way to prepopulate 'Medium' while preserving the ability to change it. Workflow rules add unnecessary automation, required fields do not set defaults, and a validation rule would restrict changes rather than allow them, so the field default is the correct configuration.
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 workflow rule that sets the Priority field to 'Medium' when a case is created.
Why it's wrong here
A workflow rule with a field update can set the value after save, but it adds unnecessary complexity and may overwrite a user's intentional selection if the rule fires on every creation. A default value is simpler and does not interfere with user edits, so the workflow rule is not the most efficient solution.
- ✓
Set the default value of the Priority picklist field to 'Medium' in the field definition.
Why this is correct
Setting a default value on the picklist field automatically populates 'Medium' when a new case is created, while still allowing users to change it. This is the simplest, most efficient configuration and requires no additional automation, directly meeting the requirement with minimal effort.
- ✗
Create a validation rule that requires the Priority field to be 'Medium' when a case is created.
Why it's wrong here
A validation rule that forces 'Medium' would prevent users from changing the priority to High or Low, which contradicts the requirement that the value can still be changed. It also does not set a default, so it fails on both counts.
- ✗
Make the Priority field required on the case page layout and instruct users to select 'Medium'.
Why it's wrong here
Making the field required forces users to select a value but does not default it to 'Medium'. This increases manual effort and does not ensure consistency, as users could choose any value. It fails to meet the goal of minimizing data entry and ensuring a default.
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.