CRT-403 practice question 10 of 35

Universal Containers has a Lightning record page that supports both the mobile app and desktop. An app builder has downloaded a custom Lightning component from AppExchange, but users are unable to view the component on mobile devices. What can be the issue?

Full set: 291 questions
Answer options
A: The record page needs to be activated.
B: The component has been developed for Desktop Pages. Correct answer
C: The component needs to be activated.
D: The record page template is unable to support mobile devices.
Correct Answer:
B. The component has been developed for Desktop Pages.
Explanation

A custom Lightning component's visibility on different devices (form factors) is determined by its metadata configuration, which is set by the developer. The component's configuration file (.js-meta.xml for LWC or .design for Aura) specifies which form factors it supports, such as Large for desktop and Small for mobile. If the developer of the AppExchange component only included support for the desktop form factor, the Lightning App Builder will not render it on mobile devices, even if the component is placed on a record page that is enabled for mobile use. This directly explains why the component is visible on desktop but not on the mobile app.

Why Incorrect

A. The record page needs to be activated. If the page were not activated, users would not be able to see the page or its components on either desktop or mobile.
C. The component needs to be activated. Individual Lightning components are not "activated." They are deployed and then added to a Lightning page, which is then activated for users.
D. The record page template is unable to support mobile devices. The question explicitly states the record page supports both the mobile app and desktop, which contradicts this option.

References

1. Salesforce Lightning Web Components Developer Guide:

Section: Configure a Component for Different Form Factors

Content: "To make a component usable on a record page in the Salesforce mobile app, add small to the formFactor list in the component’s target configuration... If you don’t define formFactor for a target, the component is supported for all form factors by default. If you define formFactor for a target, you must explicitly add the form factors you want to support." This confirms that a developer can restrict a component to desktop (Large) only.

2. Salesforce Aura Components Developer Guide:

Section: Component Bundles > Design Resource

Content: The documentation explains the tag within the .design file. It states, "Use to specify which form factors your component supports... If you don’t include , the component supports all form factors by default." This shows the mechanism for Aura components to be restricted by form factor.

3. Salesforce Help & Training:

Article: Lightning App Builder

Content: The documentation on building Lightning Pages explains that the components available in the palette and their rendering behavior are dependent on the page type and the component's own configuration. The App Builder respects the form factor settings defined in the component's source metadata.

Scroll to Top