Cloud Kicks is planning to build a custom Lightning Web Component (LWC) that needs to...

The study guide identifies C. Components Library on developer.salesforce.com as the correct answer. The key requirement is to locate a centralized resource containing Lightning component code, documentation, and specifications so the implementation team can work efficiently. The Components Library is designed for that purpose: it gives designers and developers access to component references, supported attributes, implementation details, examples, and behavioral expectations. Option A, Salesforce Extensions for VS Code, is a development-tooling environment. It helps developers work with Salesforce metadata and code, but it is not the primary reference library for exploring Lightning component specifications. Option B, Design Tokens, provides reusable design values such as spacing, colors, and other design attributes. Tokens help maintain visual consistency, but they do not function as a comprehensive component reference. From a UX implementation perspective, using documented Lightning components reduces unnecessary custom development and helps ensure that components behave consistently with Salesforce interaction patterns. It also improves implementation speed because teams can begin with an established component rather than inventing a new one.

Study Guide reference/topics: Lightning Components, LWC implementation, component documentation, SLDS, reusable UI architecture.

==================================