SF-Admin Object Manager and Lightning App Builder Practice Question
Which Lightning App Builder feature allows an administrator to show specific components only when a user meets certain criteria, such as their role or department?
⚠ Common exam trap
Candidates frequently select Page Layout properties or Record Types instead of App Builder features when asked how to conditionally show components based on user attributes.
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
✓
Component Visibility Filters.
Component Visibility Filters in the Lightning App Builder provide a declarative way to control the display of components on a page. By leveraging record fields, user attributes, or permissions, administrators can tailor the user experience to be less cluttered and more relevant. This capability is essential for creating dynamic, role-based dashboards and interfaces that improve usability and data security by hiding irrelevant information from specific user groups.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Dynamic Forms.
Why it's wrong here
Dynamic Forms allow for the configuration of individual fields and sections on a page layout, but they are not the primary mechanism for hiding or showing entire custom components based on user attributes. While related, visibility filters are the specific feature used for controlling component display logic.
- ✗
Record Type assignment.
Why it's wrong here
Record types are used to control which page layouts, picklist values, and business processes are available to a user. They do not provide the granular, real-time control needed to show or hide specific Lightning components on a single page based on external user-related criteria or field values.
- ✓
Component Visibility Filters.
Why this is correct
Component visibility filters enable administrators to define logic that determines whether a component appears on the page. By setting criteria based on user fields or record data, the page adapts dynamically to the context of the user, providing a personalized experience without requiring custom code or multiple different page layouts.
- ✗
Profile-based Page Layouts.
Why it's wrong here
Page layouts are static assignments. Using them to show or hide components would require creating and maintaining separate page layouts for every user group, which is an inefficient and non-scalable practice. Component visibility filters offer a much more streamlined, dynamic, and maintainable approach to achieving the same outcome.
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.