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 questionsA 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.
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.
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.
Keep practicing
Take the free CRT-403 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other CRT-403 practice questions
- Question 1Universal Containers is adding drone delivery to service offerings, and the developer has…
- Question 2An app builder at Ursa Major Solar has been working on a new custom app in a sandbox that…
- Question 3An app builder would like to streamline the user experience by reflecting summarized calc…
- Question 4The services manager wants to make sure the team enters case priority consistently. What …
- Question 5Ursa Major Solar wants to convert the relationship between Galaxy and Star from a lookup …
- Question 6Universal Containers has two types of applicants, hourly and salary. There are separate r…
