SF-Admin Object Manager and Lightning App Builder Practice Question
A user reports that they cannot see a custom field that was recently added to an object. What is the first thing an administrator should check?
⚠ Common exam trap
Candidates often check the Page Layout first. While important, Field-Level Security (FLS) is the more common 'hidden' culprit that prevents a field from appearing even if it is on the layout.
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
✓
Verify Field-Level Security for the user's profile.
Field visibility is governed by two main factors: page layouts and field-level security. Checking field-level security in the Object Manager is the most common resolution, as it is a frequent point of failure when deploying new fields. By verifying these permissions, the administrator ensures the user has the necessary access rights, which is a fundamental troubleshooting step for resolving data access issues within Salesforce.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Check the user's login history.
Why it's wrong here
Login history tracks when and how a user accessed the system. It does not provide any information regarding the user's permissions or their ability to view specific fields on a record. Checking this would be irrelevant to troubleshooting a potential field-level security or page layout configuration problem.
- ✓
Verify Field-Level Security for the user's profile.
Why this is correct
Field-level security settings determine whether a user can see or edit a specific field. Even if a field is added to a page layout, if the user's profile does not have the 'Visible' check box enabled for that field, it will remain hidden from their view entirely.
- ✗
Delete and recreate the field.
Why it's wrong here
Deleting and recreating a field is a destructive and unnecessary action. It causes data loss and does not solve the root cause, which is almost always a permissions or layout visibility issue. Administrators should always investigate configuration settings before resorting to removing and recreating existing data components.
- ✗
Change the user's role in the hierarchy.
Why it's wrong here
Role hierarchy controls access to records (data sharing), not the visibility of fields on a layout. Changing the user's role will not affect which fields are visible on a record page, so this action would be completely ineffective in resolving the reported issue regarding missing custom fields.
Visual reference
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.