Explanation:

Salesforce Knowledge must be enabled in the organization before the OmniScript Knowledge Step can be activated and used to search and view articles. This is a fundamental prerequisite that enables the knowledge management framework within Salesforce.

Activation Process
The feature is enabled in Setup by searching for "Knowledge Settings" and checking the Enable Lightning Knowledge option. Additionally, users must be assigned the Knowledge User permission to access and interact with knowledge articles.

Why other options are incorrect:

B. Omniscript Designer: This is the tool used to build the script, not the prerequisite feature that must be active in the org for the Knowledge Step to work.

C. Salesforce Classic & D. Salesforce Lightning:
These are user interface frameworks. The requirement is not about the UI's appearance, but about enabling the specific Knowledge feature.

Reference:
Salesforce documentation confirms Salesforce Knowledge is the enabling framework required before Knowledge can be integrated into OmniScripts. Without this activation, the Knowledge Step option is unavailable in OmniScript Designer.

Explanation:

C. Formula:
This element is used to perform a calculation within the OmniScript. It can use OmniScript functions to calculate the user's age based on their birthdate. The AGE() function can be used to dynamically calculate the age from a date input. The result of this calculation, for example %FormulaAge%, is then used to control the flow and messaging of the OmniScript.

A. Alert:
The Alert element is used to display a message to the user. To meet the requirement, the Alert element is configured to display the message "You must be 18 years or older to purchase" only when the calculated age is less than 18. This is achieved using a Conditional View on the Alert element. The condition would be something like %FormulaAge% < 18, meaning the alert only appears for underage users. The OmniScript can then be configured with validation on steps or conditional branching to prevent the user from continuing, effectively restricting progress.

Why other options are incorrect:

B. Calculation:
While a Calculation element could be used, the Formula element is the more specific and appropriate component for a simple dynamic age calculation within a step. The question likely expects the most precise OmniScript element for the task.

D. Messaging:
There is no standard "Messaging" element in OmniScript. The correct component for displaying a message is the Alert element.

Reference:
OmniScript documentation confirms that Formula elements are used to perform calculations using expressions and functions, and Alert elements are used for display and conditional messaging

Explanation:

OmniScripts are the primary OmniStudio tool for creating guided, step-by-step business processes that deliver interactive, user-facing experiences . They are specifically designed to "guide users through sales and service processes, enabling them to quickly and easily achieve their goals" . This makes them ideal for automating complex business processes that require both user interaction and data integration.

Why other options are incorrect:

A. Integration Procedures:
These are server-side orchestrators that execute multiple actions (API calls, data saves) in a single server call . While they power the backend logic and can be called by OmniScripts, they are headless and do not provide any user-facing guided interactions .

B. FlexCards:
These are UI components designed to "display contextual information in the flow of work" as lightweight cards . They surface critical data and embed actions, but they do not create multi-step guided workflows .

C. Expression Sets:
These are part of the Business Rules Engine for performing calculations and lookups . They handle business logic but do not create interactive user journeys.

Reference:
Salesforce OmniStudio documentation confirms that "OmniScripts are guided, step-by-step workflows that lead users or agents through complex tasks" , forming the user-facing component of the OmniStudio architecture while Integration Procedures and Data Mappers serve as the underlying data and logic layer .

Explanation:

The primary and most logical consideration when choosing a data source for a FlexCard is whether it can actually retrieve data from the target Salesforce object. The client's core requirement is to display data from a specific object, so the consultant's advice must start there: selecting a data source type that supports querying that object's records.

Why other options are incorrect:

A. Based on the speed of data retrieval:
While performance is an important factor in any technical design, it is a secondary consideration. The data source must first be capable of retrieving the data. The "best" data source is one that retrieves the necessary data correctly; optimizing speed comes after.

B. The client should choose the data source that retrieves the most data:
Retrieving more data than needed is an anti-pattern. It's more efficient and secure to only retrieve the specific data required for the FlexCard.

C. Based on the number of records it can retrieve:
The ability to handle a certain number of records is a capacity consideration, but the primary selection criterion is whether the data source can access the right object. The approach may differ if the requirement is to display one record or a list of records, but querying the correct object is the foundational requirement.

Explanation:

The Style panel in the Flexcard Designer is the specific tool purpose-built for customizing the visual appearance of individual elements on a FlexCard. It provides a declarative, no-code interface for configuring the look and feel of each element in real time . When you select an element on the canvas, the Style panel appears with settings for backgrounds, sizes, borders, padding, margins, height, fonts, and responsiveness . It includes sections for Alignment, Appearance, Custom Styles, and Dimensions, allowing precise control over element styling . Additionally, you can save custom styles and apply them to multiple elements on the same FlexCard . For custom designs beyond the declarative options, you can also create and apply custom CSS directly in the Style panel .

Why other options are incorrect:

A. Data Mapper:
Data Mappers are used to extract, transform, and load Salesforce data. They are data services, not visual design tools, and do not affect how elements look on the UI.

B. Integration Procedures:
These execute server-side actions like API calls or data orchestration. They are backend services and do not have any UI styling capabilities.

D. OmniScripts:
OmniScripts are designed for guided, step-by-step user interactions. They are not used to style FlexCard elements.