SF-Admin Configuration and Setup Practice Question
Cloud Kicks has a custom object called Merchandise__c that includes a currency field Unit_Price__c. The administrator discovers that when a user creates a new Merchandise record, the Unit_Price__c field does not appear on the page layout. The administrator confirms that the field-level security for the user's profile allows visibility and that the field is not marked as required. What is the most likely cause for the field not appearing?
⚠ Common exam trap
The trap here is assuming that field-level security alone controls field visibility on page layouts, when in fact page layouts must also include the field.
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
✓
The field is not added to the page layout assigned to the user's profile.
The field is missing from the page layout assigned to the user's profile. Page layouts control which fields are displayed on record detail and edit pages. Even with proper field-level security, a field must be explicitly added to the page layout to be visible. Since FLS allows visibility, the most likely cause is that the administrator did not include the field on the page layout.
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-level security for the user's profile is set to 'Read Only'.
Why it's wrong here
Field-level security set to 'Read Only' still allows the field to be visible, but not editable. The scenario states the field does not appear at all, and the administrator confirmed FLS allows visibility. Therefore, 'Read Only' would not cause the field to be hidden; it would only prevent editing, which is not the issue described.
- ✗
The user's profile does not have the 'Customize Application' permission.
Why it's wrong here
The 'Customize Application' permission allows users to modify the app's setup, not to view fields on records. It is unrelated to field visibility on page layouts. Even without this permission, users can see fields if FLS and page layout settings permit. This permission is typically granted to administrators, not standard users, and does not affect record page display.
- ✗
The field is not included in the search layout for the object.
Why it's wrong here
Search layouts determine which fields appear in search results and lookup dialogs, not on record detail pages. The issue described is about the field missing when creating a new record, which is governed by the page layout. Search layouts are separate and would not affect the visibility of a field on a record creation page.
- ✓
The field is not added to the page layout assigned to the user's profile.
Why this is correct
Page layouts control which fields are visible on record detail and edit pages. Even if field-level security allows access, a field must be explicitly added to the page layout to appear. In this scenario, the administrator has confirmed FLS allows visibility, so the missing field indicates it was not placed on the page layout assigned to the user's profile.
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.