SF-Admin Configuration and Setup Practice Question
A user is unable to see a custom field on a record page, even though it is visible on the Page Layout. What is the most likely reason?
⚠ Common exam trap
Candidates assume that placing a field on a Page Layout guarantees visibility, forgetting that Field-Level Security always takes precedence over layout settings.
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
✓
Field-Level Security is hidden for the user's profile.
Field-Level Security (FLS) is the most common reason for a field to be hidden despite being on the layout. If the user's profile or assigned permission set has the visibility attribute unchecked for that field, the field will remain hidden. Troubleshooting this is a core competency for administrators, as it requires checking security settings rather than just UI configuration, ensuring data visibility complies with company privacy policies.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The field is not added to the Lightning Record Page.
Why it's wrong here
If a field is not on the Lightning Record Page, the user might still see it in the 'Details' tab or standard components. However, this is less likely to be the root cause if the user can see other fields on the same page layout but not the specific field in question.
- ✓
Field-Level Security is hidden for the user's profile.
Why this is correct
Field-Level Security acts as a security layer that sits above the page layout. Even if a field is explicitly included in a Page Layout, the user will be unable to see or interact with the field if their profile or permission sets do not grant visibility to that specific field.
- ✗
The user has insufficient object permissions.
Why it's wrong here
If the user lacked object permissions, they would likely be unable to see the object or the records entirely, not just a single field. Since the user can see the record and the page layout, the issue is specifically related to the field's security settings rather than the object.
- ✗
The field is a system-generated field.
Why it's wrong here
System-generated fields like 'Created By' or 'Last Modified By' are standard and usually visible to all users unless specifically hidden by FLS. They are not 'hidden' by default in a way that would require special configuration just to view them, making this an unlikely cause for a custom field issue.
About these practice questions
Courseiva writes every SF-Admin question from scratch — 202 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.