Determine the Steps to Install and Set up Lightning Components. EXPERIENCE-CLOUD-CONSULTANT Practice Questions (Page 1)

Questions 1–5

1. 1expert · medium

   A company is using a managed package that includes a Lightning component for a custom search. The component is visible in the palette and works for internal users, but external users see a blank page. The admin has confirmed that the external user's profile has access to the component and the data. What is the most likely cause?

   • AThe component uses an Apex class that is not accessible to the external user's profile.
   • BThe component is not compatible with the site's template.
   • CThe external user's license does not support the component.
   • DThe component is not 'Available for Experience Cloud'.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   An admin is configuring a Lightning component that displays a map of store locations. The component has a property called 'API Key' that must be entered. The admin wants to ensure the key is not visible to end users. What is the best practice for handling this?

   • AHardcode the API key in the component's code.
   • BStore the API key in a custom setting and reference it in the component.
   • CUse a Named Credential to store the API key and have the component call an Apex class that uses it.
   • DEnter the API key in the component's properties panel and mark it as 'Protected'.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A consultant is setting up a new Experience Cloud site and needs to install a custom Lightning component that was developed in a separate Salesforce org. The component is not on the AppExchange. Which method should the consultant use to make the component available in the target org?

   • AUse the 'Upload from File' option in the Experience Builder.
   • BCopy the component's code and paste it directly into the target org's Developer Console.
   • CUse the 'Deploy to Site' button in the source org's setup menu.
   • DCreate a new package in the source org and install it in the target org using an installation URL.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   An admin has installed an unmanaged Lightning component from a GitHub repository into a sandbox. The component appears in the palette, but when dragged onto the page, it shows an error: 'This component cannot be used in this context.' The component is designed to be used on a Record Page. What is the most likely cause?

   • AThe component is an Aura component and requires a different builder.
   • BThe component is not compatible with the site's template.
   • CThe component is designed for a specific target (e.g., Record Page) and is being placed on a standard page, which is not a supported target.
   • DThe component was installed in the wrong sandbox.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A company has installed a managed package that includes a Lightning component for a custom dashboard. The component is not visible in the palette. The admin has checked the package installation and confirmed it was successful. What is the next step the admin should take?

   • ACreate a new page template to make the component available.
   • BReinstall the package in a different sandbox.
   • CContact Salesforce support to enable the component.
   • DCheck the component's metadata to ensure it is marked as 'Available for Experience Cloud'.
   Reveal Solution Discussion Select an answer first