DEX-403 practice question 16 of 35

An app builder has downloaded a component from the AppExchange successfully; however, they are unable to add it to the Lightning home page. Which two reasons can be preventing the app builder from being able to add the custom component? Choose 2 answers

Full set: 291 questions
Answer options
A: My Domain must be deployed to add custom components to the page with the App Builder. Correct answer
B: A custom tab must be created to add custom components to the page with the App Builder.
C: The component requires a developer permission to add it to the page with the App Builder.
D: The component is tagged for record pages instead of home pages and is not showing up in the App Builder. Correct answer
Correct Answer:
A. My Domain must be deployed to add custom components to the page with the App Builder.; D. The component is tagged for record pages instead of home pages and is not showing up in the App Builder.
Explanation

For a custom Lightning component to be added to a Lightning page, two key conditions must be met. First, My Domain must be deployed in the Salesforce org. This is a mandatory prerequisite for using custom Lightning components within Lightning pages, the Lightning App Builder, and other Lightning Experience features, as it provides a unique domain for security and component referencing. Second, the component itself must be configured to be available for the specific page type. This is done in the component's metadata, which must explicitly target "Home Pages" (lightningHomePage). If the component is only targeted for other page types, such as record pages, it will not appear in the component palette when editing a home page.

Why Incorrect

B: A custom tab makes a component accessible from the navigation bar; it is not a requirement for adding the component to a Lightning page. C: Standard administrative or app builder permissions (e.g., "Customize Application") are required, not a specific "developer permission" to add components via the App Builder.

References

1. My Domain Requirement (for Answer A):

Source: Salesforce Help Documentation

Reference: Article "My Domain"

Content: "To use Lightning components in Lightning component tabs, Lightning pages, the Lightning App Builder, or standalone apps, you must have a My Domain." This statement explicitly confirms that My Domain is a prerequisite for using the App Builder to add custom components.

2. Component Configuration for Page Types (for Answer D):

Source: Salesforce Lightning Web Components Developer Guide

Reference: Section "Configure a Component for Lightning App Builder"

Content: The js-meta.xml configuration file for a Lightning Web Component must include the lightningHomePage tag within the element for the component to be exposed in the Lightning App Builder for home pages. The absence of this target prevents it from being listed.

3. Aura Component Configuration (supports Answer D):

Source: Salesforce Aura Components Developer Guide

Reference: Section "Component Bundles > Design File"

Content: For Aura components, the .design file must include the flexipage:availableForAllPageTypes interface or specifically target home pages using interfaces like force:appHostable and flexipage:availableForRecordHome (which also makes it available on Home pages). This configuration controls where the component can be used.

4. Permissions for Lightning App Builder (refutes Answer C):

Source: Salesforce Help Documentation

Reference: Article "Create and Configure Lightning Experience Record Pages"

Content: The required permissions to edit Lightning pages are "Customize Application" and "View Setup and Configuration." There is no mention of a special "developer permission" being necessary for this task.

Scroll to Top