The key difference between Integration Procedures and DataRaptors is that Integration Procedures can access data from external sources, while DataRaptors can only access data from Salesforce. Integration Procedures allow the designer to create complex API queries declaratively using HTTP Actions or SOAP Actions.
DataRaptors allow the designer to read, transform, and write data between Salesforce objects or fields. Both Integration Procedures and DataRaptors can invoke multiple actions in a single server call, and both can retrieve data from multiple related objects.

Explanation
FlexCards are used to display contextual customer information in a compact and customizable way. They can also provide access to related processes or actions. In this scenario, the features that the consultant should recommend are:
* Actions: These are buttons or links that can launch OmniScripts, DataRaptors, or other processes from the FlexCard. They can help the users to perform tasks related to the customer information displayed on the FlexCard.
* Custom Styles: These are CSS classes that can be applied to the FlexCard elements to match the
* company's color scheme and fonts. They can help the users to have a consistent and branded user interface.
* Data Tables: These are elements that can display tabular data from one or more data sources on the FlexCard. They can help the users to see relevant data in a structured and sortable way.
The features that the consultant should not recommend are:
* Menu Elements: These are elements that can display a list of options or submenus on the FlexCard.
They are not suitable for this scenario because they do not provide access to processes or actions, but only to other FlexCards or pages.
* Newport Design System: This is a design system that provides a set of predefined styles and components for OmniStudio applications. It is not suitable for this scenario because it does not match the company's color scheme and fonts, and it may require additional customization.

Explanation
The two reasons that explain why Integration Procedures are recommended as the first choice of data sources for FlexCards and OmniScripts are: they future-proof your front-end design and they combine multiple actions into a single server call. An Integration Procedure can abstract the data source from the front-end design, making it easier to change or update the data source without affecting the FlexCard or OmniScript. An Integration Procedure can also execute multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services in one call, reducing the number of requests and processing time