SF-Admin Object Manager and Lightning App Builder Practice Question
Cloud Kicks wants a specific Lightning Page to appear only for users with the 'Sales Executive' profile when they view an Opportunity record. How should the administrator configure this?
⚠ Common exam trap
Candidates often try to use Sharing Rules or Permission Sets to control page visibility. These tools manage record access and feature permissions, not the UI layout displayed to the end-user.
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
✓
Assign the Lightning Page to the Opportunity record using the 'App, Record Type, and Profile' assignment option in Activation.
Lightning App Builder allows administrators to assign Lightning pages based on specific criteria such as App, Record Type, and Profile. By setting a Profile-based assignment, the administrator ensures that the customized layout is surfaced exclusively to the targeted user group, maintaining a streamlined user experience while adhering to internal security and visibility protocols necessary for effective organizational data management.
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 new record type and assign the page via the Record Type assignment settings.
Why it's wrong here
Record Types are designed to control picklist values and page layouts, not Lightning Page assignments. While record types can influence page visibility, relying on them for profile-specific overrides is inefficient and introduces unnecessary complexity to the data model when profile-based assignment in App Builder is the intended feature for this requirement.
- ✗
Add a visibility filter on the Lightning Page components to hide them from all other profiles.
Why it's wrong here
Component-level visibility filters hide individual elements rather than the entire page. If the requirement is to show a distinct Lightning Page, managing filters on every single component is error-prone and difficult to maintain as the organization scales or changes, whereas page-level assignment handles this at the framework level.
- ✓
Assign the Lightning Page to the Opportunity record using the 'App, Record Type, and Profile' assignment option in Activation.
Why this is correct
The Activation dialog in Lightning App Builder provides a specific tab for assigning pages based on a combination of App, Record Type, and Profile. This is the native, supported method for directing users of a specific profile to a unique Lightning Page without needing complex workarounds or record type dependency.
- ✗
Use a Dynamic Form to conditionally show the entire record page layout based on the user's profile.
Why it's wrong here
Dynamic Forms enable conditional visibility for fields and field sections within a single page, but they cannot hide or replace the entire Lightning Page structure. Attempting to use Dynamic Forms for page-level control is architecturally incorrect and would result in an unmanageable configuration of nested visibility rules.
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.