SF-Admin Configuration and Setup Practice Question
A company wants to ensure that a new custom field is only visible to the 'Sales' profile. How should the administrator handle this during field creation?
⚠ Common exam trap
Candidates often try to use page layouts to restrict visibility. However, page layouts only control the UI, not the security; a user can still see the field via reports or APIs.
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 FLS to Visible only for the Sales profile
When creating a custom field, the Field-Level Security step allows an administrator to define which profiles have visibility. By default, Salesforce might expose the field to many profiles. The administrator must explicitly uncheck the 'Visible' checkbox for all profiles except the 'Sales' profile to ensure that other users do not see or interact with the new data field.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Update the Page Layout for all other profiles
Why it's wrong here
Updating the page layout hides the field from the UI, but it does not remove the user's ability to access the data via API, reports, or list views. Field-level security must be managed through profiles, not page layouts, to effectively secure data at the metadata access level.
- ✓
Set FLS to Visible only for the Sales profile
Why this is correct
Defining visibility in the Field-Level Security (FLS) section during the field creation wizard is the correct way to restrict access. By selecting 'Visible' only for the 'Sales' profile, the administrator ensures that other users have no access to the data, regardless of their object-level permissions or page layouts.
- ✗
Create a new Permission Set for the Sales profile
Why it's wrong here
While a Permission Set could grant access, it is an extra step that adds unnecessary complexity. It is standard practice to manage field visibility directly during the creation wizard using the FLS settings. Using a Permission Set would require additional ongoing maintenance for future users, which is less efficient.
- ✗
Remove the field from the Sales Profile object permissions
Why it's wrong here
Removing object permissions from a profile would prevent the Sales profile from interacting with the object entirely, not just the field. This would block users from viewing or editing any records, which is not the desired outcome when the goal is to restrict visibility to a specific field.
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.