The correct answer is B. Exhaust the list of available base Lightning components in the Component Library. This is the best practice explicitly selected in the uploaded study guide.

The scenario begins with a proposed custom Lightning component, but the guide indicates that customization should not be the first assumption. Before developing something new, the designer and implementation team should first determine whether an existing base Lightning component already satisfies the requirement.

This approach promotes consistency with the standard Salesforce user experience and avoids unnecessary duplication. Existing components already embody Salesforce interaction and presentation conventions, making them the logical starting point for a Lightning-based solution.

Option A immediately moves toward custom HTML and separately linked styling resources. That bypasses the study guide's preferred sequence of first checking whether established Salesforce functionality already exists.

Option C is too absolute. SLDS blueprints are useful resources for component construction, but the guide does not recommend choosing blueprint markup over existing base Lightning components in every case.

The principle being tested is reuse before customization. Custom development should be justified by a genuine gap in standard functionality, not merely by the existence of a specialized business requirement.

Study Guide reference/topics: Base Lightning Components, Component Library, custom components, SLDS, reuse before customization.

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