The UX Designer at Cloud Kicks is considering using a custom Lightning component to fulfill a specific business requirement. Which two best practices…

Two best practices that should be considered when using a custom Lightning component to fulfill a

specific business requirement are:

Find the closest Salesforce Lightning Design System (SLDS) Blueprint to help inform the custom

Lightning component. The SLDS is a collection of design guidelines, UI components, and code

samples that help you create consistent and beautiful user interfaces for Lightning applications. The

SLDS Blueprints are examples of common UI patterns and components that are built with the SLDS

and follow the design principles and best practices. The Blueprints can help you inform the custom

Lightning component by providing inspiration, guidance, and code snippets that you can modify and

reuse. The Blueprints can also help you ensure that the custom Lightning component is compatible

and consistent with the rest of the Lightning application and the Salesforce platform. [UX Designer

Certification Prep: Salesforce Design System], Lightning Design System Website

Exhaust the list of available base Lightning components in the Component Library. The base Lightning

components are a set of pre-built UI components that you can use to create custom Lightning

components. The base Lightning components are built with the SLDS and provide the functionality

and interactivity that you need for common UI elements, such as buttons, icons, forms, tables,

charts, and more. The base Lightning components also handle the accessibility, security, and

performance aspects for you, so you don’t have to worry about them. The Component Library is a

reference guide that provides documentation and examples for the base Lightning components, as

well as other Lightning web components and Aura components. The Component Library can help you

explore the list of available base Lightning components and see how they work and how to use them.

The Component Library can also help you avoid reinventing the wheel and save time and effort by

using the base Lightning components as much as possible, and only creating custom Lightning

components when there is no suitable base Lightning component for your requirement. [UX Designer

Certification Prep: User Testing and Evaluation], Developer Center’s Lightning Component Library

Prioritizing Aura markup even if there is a Lightning Web Component (LWC) available, and creating

HTML markup and linking the SLDS stylesheet via static resource are not best practices that should be

considered when using a custom Lightning component to fulfill a specific business requirement.

These practices can lead to suboptimal performance, maintainability, and compatibility issues for the

custom Lightning component. Aura markup is the older syntax for creating Aura components, which

are the predecessor of Lightning web components. Lightning web components are the newer and

faster way of creating custom UI components for Lightning applications, using modern web standards

and best practices. Lightning web components also have better interoperability and compatibility

with Aura components and other web components, as well as with the base Lightning components

and the SLDS. Therefore, it is recommended to use Lightning web components over Aura

components whenever possible, and to use LWC markup instead of Aura markup for creating custom

Lightning components. [UX Designer Certification Prep: User Testing and Evaluation], Lightning Web

Components Developer Guide

Creating HTML markup and linking the SLDS stylesheet via static resource is also not a recommended

practice for creating custom Lightning components, because it can create unnecessary complexity

and duplication for the custom Lightning component. A static resource is a file or a collection of files

that can be referenced by a Lightning component, such as images, style sheets, JavaScript libraries,

or fonts. However, linking the SLDS stylesheet via static resource means that you have to manually

download and upload the SLDS files to your org, and update them whenever there is a new version

of the SLDS. This can create maintenance and compatibility issues for the custom Lightning

component, as