The Interaction Console provides a holistic view of the customer‘s information—and FlexCards are important components of these 360-degree views. The FlexCards you see on the console are Lightning web components (LWC) based on FlexCards; the console itself is a Salesforce Lightning console.

For This Data Input Source | Use This OmniScript Action Element
Salesforce Org—One field only | Lookup
Salesforce Org—Many fields | DataRaptor Extract Action
API | HTTP Action
Anything that Apex can access | Remote Action
User | Any Inputs Element
https://trailhead.salesforce.com/content/learn/modules/omnistudio-omniscript/create-a-simple-omniscript?trail_id=get-to-know-omnistudio

If there are multiple versions of a matrix, only one version can be accessed at a time, based on these factors:The date/time range on the matrices. (That is, are they active at the same time?)If they are both active, the highest priority active matrix is the one that runs. (1 is the lowest priority.)
Look Up Data with Calculation Matrices Unit | Salesforce Trailhead

This is what the process looks like when you combine the two conditions.
For each Object in the Input JSON, the DataRaptor Load looks at each field.If the field is marked Is Required For Upsert, the DataRaptor Load checks to see if the field has data.All Is Required For Upsert fields must have data. If not, the DataRaptor Load skips that record.
If the field does have data, the DataRaptor Load checks to see if the field is an Upsert Key, and then compares all the fields that are Upsert Keys.If all of the Upsert Keys together find a match with an existing record in Salesforce, the DataRaptor updates the target record rather than create a duplicate record.If the DataRaptor Load can’t find a match with any existing record, it creates a new record.
Build a DataRaptor Turbo Extract and DataRaptor Load Unit | Salesforce

When you’re ready to configure DataRaptors, you use the OmniStudio DataRaptor Designer. You can access it via the OmniStudio DataRaptors tab in the OmniStudio app. The designer has tabs too. Use the following designer tabs to specify what you want the DataRaptor to do.
Extract tab
Formulas tab
Output tab
Options tab
Preview tab

Options Tab
On the Options tab, you set advanced options such as whether to check the user‘s access permissions for the fields before executing the DataRaptor. Set the Platform Cache Type to Session Cache for data related to users and their login sessions, or Org Cache for all other types of data. The Time to Live in Minutes setting determines how long the data remains in the cache.
Explore DataRaptor Features Unit | Salesforce Trailhead

Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

Card properties is in the Setup panel.
The Style panel is made up of these sections:
Alignment
Update the padding, margin, and text alignment of an element.
Appearance
Configure the color, background, and border of an element.
Custom
Create and apply custom classes, and add inline styles to an element.
Custom CSS
Save style settings on a FlexCard element as a custom style to use on multiple elements of a FlexCard.
Dimensions
Set the height and width, and configure the responsiveness of your element.

OmniScript –>IntegrationProcedure<->DataRaptor Extract<->Salesforce
This option is incorrect because the data is not sent back to OmniScript.
FlexCard–>OmniScript <->DataRaptor Extract<->Salesforce
This option is incorrect because you need an Integration Procedure between OmniScript and DataRaptor Extract. Also the question states to assume RecordId variable has been passed so FlexCard is irrelevant.
IntegrationProcedure <-> OmniScript <-> DataRaptor Extract <-> Salesforce
This option is incorrectbecause OmniScript must be before the Integration Procedure in the data flow.
Create a Simple OmniScript Unit | Salesforce Trailhead

Actions have their own naming conventions. Use a prefix for the element type, such as DR for DataRaptor or IP for Integration Procedure. Then use VerbObjectDetail.
E.g. In the Edit Account OmniScript, IPGetAccountDetails is the name of the Integration Procedure Action above the Step, and IPSaveAccountDetails is the name of the Integration Procedure Action below the Step.

An OmniScript’s look and feel (frontend) is separated from its functionality (backend). OmniScripts separate the JavaScript Object Notation (JSON) metadata structure (1), the stylesheets (2), and the data (3) from each other.
This modular architecture supports prototyping and building the user experience quickly. It also promotes using data from anywhere, reuse of JSON metadata, and ease in applying branding standards.
Learn the Fundamentals of OmniScripts Unit | Salesforce Trailhead

OmniStudio’s Service Management layer includes data services that read, write, transform, calculate, and track data within and outside of Salesforce. This layer includes processes and tools for users to look up data and configure complex math on top of the Salesforce Platform: OmniStudio Matrices and OmniStudio Calculation Procedures.
Look Up Data with Calculation Matrices Unit | Salesforce Trailhead

Element Type | What Is It For?
Actions | For calling on other tools to perform various actions: getting or saving data, calculating, sending an email, and so on
Display | For displaying text and images on the screen to enhance the usability of the UI
Functions | For performing calculations within the OmniScript, showing conditional messages, and providing geolocation
Group | For grouping elements together on the UI
Inputs | For system or user input or selection
OmniScripts | Reusable OmniScripts to insert and use

When reading a Calculation Procedure, it’s important to know its five basic components, outlined here.
Required:
Variables and Constants: Used in calculation steps
Optional:
Calculation Steps: Matrix and Lookup
Aggregation Steps: Allow you to use data from an array input where the calculations are run on each element separately
Preprocessor Class: Apex classes used to manipulate the input of the calculation
Postprocessor Class: Apex classes used to manipulate the output of the calculation
Perform Complex Math with Calculation Procedures Unit | Salesforce

There are three types of Calculation Matrices, and their uses vary.
Standard Calculation Matrix: Used when your matrix doesn‘t need to be a part of a group or versioned row by row.
Grouped Calculation Matrix: Used to group similar matrices with the same Input and Output headers together.
Row-Versioned Calculation Matrix: Used if you have a matrix with many rows and may need to change small portions of the data at a time. Each row has its own start date and time
All Calulation Matrices are lookup tables, so “when you need to perform a lookup“ does not help you decided which calculation matrix to use.

Complete a Process
Guided interactions in OmniScripts typically mirror customer or business processes that often require visiting more than one screen and accessing more than one database. For example, a customer might want to view their bill, choose to pay it, and select a specific way to pay it.
Explore OmniScript Guided Interactions Unit | Salesforce Trailhead

An OmniScript’s Type, Subtype, and Language gives an OmniScript its unique identity. Only one active OmniScript may have the same Type, SubType, and Language at any time. An OmniScript’s Type must start with a lowercase letter.
An OmniScript’s Name does not have to be unique in your org

OmniStudio Integration Procedures are declarative, server-side processes that execute multiple actions in a single server call. Let’s break this down to better understand what it means.
Declarative: Use drag-and-drop elements in the Integration Procedure Designer to build the process structure.
Server-side processing: This enables faster performance, because the server, in most cases, is faster than the client at processing data.
Multiple actions in a single server call: This prevents round trips to the server. Minimizing client/server calls is beneficial, as more round trips mean slower performance.
Get Started with OmniStudio Integration Procedures Unit | Salesforce

A DataRaptor function is an equation you use for operations to do the following.
Manipulate data about date and time
String text together
Determine a result based on logic
Perform mathematical operations on numbers using fractions
Explore DataRaptor Features Unit | Salesforce Trailhead
Calculation procedures use calculation matrices.

Features of the Style Panel
You configure the look and feel of a FlexCard by styling individual elements and the fields within elements. Using the Style panel, we design backgrounds, text, and borders, and adjust heights, widths, and the spacing inside and between elements. There are also specific style options available for the following elements.
Action
Datatable
Field
Icon
Menu
Toggle

Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

Configure optional additional filter settings by clicking the down arrow to the right of the first filter:
• AND – Add another filter and specify that both filters must be true.
• OR – Add another filter and specify that either filter can be true.
• LIMIT – Specify the maximum number of records returned. Allowed values are 1 through 2000. For more information, see Workaround for offset 2000 limit on SOQL query in the Salesforce knowledge base.
• OFFSET – Use with LIMIT to specify the first record on a page in a multi-page retrieval. For example, a LIMIT of 5 requires OFFSET values of 0, 5, 10, and so on.
• ORDER BY – Sort the results by the specified field. To sort by multiple fields, specify a comma?separated list of field names in order of precedence, for example LastName,FirstName. You can optionally specify ASC or DESC for an ascending or descending sort. You can optionally specify NULLS FIRST or NULLS LAST to place blank values at the beginning or end. For example, you can sort Accounts by the number of employees, listing the companies of unknown size first and the largest employers last. Specify the ORDER BY value NumberOfEmployees ASC NULLS FIRST.
OmniStudio Foundation (salesforce.com) Page 524(540)

DataRaptor Extract, DataRaptor Load, and DataRaptor Transform also do the following.
-Trim, map, restructure, and transform data in JSON, XML, or Custom Schema.
-Use formulas and functions to transform data.
DataRaptor Turbo Extract
DataRaptor Turbo Extract retrieves and filters data from a single Salesforce object type with support for fields from related objects. You can filter the data and select the fields to return. Unlike a standard DataRaptor Extract (which we describe next), a DataRaptor Turbo Extract doesn’t support formulas or complex output mappings.
It has two advantages over a standard DataRaptor Extract.
-Simpler configuration
-Better performance at runtime
Discover DataRaptor Types Unit | Salesforce Trailhead

✅ D. Lookup

• The Lookup Action Element in OmniScript is specifically designed to retrieve a single field value from a Salesforce object based on a specified condition. It’s optimized for fetching a limited amount of data, such as a single field.

❌ A. DataRaptor Extract Action

• While the DataRaptor Extract Action can retrieve data from Salesforce, it is generally used for fetching multiple fields and potentially multiple records based on more complex criteria. Using it to retrieve only one field would be less efficient than using the Lookup Action.

❌ B. HTTP Action

• The HTTP Action is used to integrate with external systems via REST or SOAP APIs. It is not the appropriate element for directly querying data within the Salesforce Org for a single field.

❌ C. DataRaptor Turbo Extract

• DataRaptor Turbo Extract is a specialized type of DataRaptor Extract that is optimized for retrieving large volumes of data from a single Salesforce object. It is not designed or efficient for retrieving a single field.

From the following options, indicate which type of datasource you would like to use.
None
SOQL Query
Use the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information.
SOSL Search
Use the Salesforce Object Search Language (SOSL) to construct text-based search queries against the search index.
Apex Remote
Apex Remote data source is used to make a Apex Remote call.
Apex REST
Apex REST data source is used to make a Apex REST call.
DataRaptor
DataRaptor data source is used to make calls to Vlocity DataRaptors.
REST
Uses the standard REST API call.
Integration Procedures
Integration Procedure data source is used to make calls to Vlocity Integration Procedures.
Streaming API
Streaming API enables streaming of events using push technology and provides a subscription mechanism for receiving events in near real time.
Custom
Uses the sample JSON provided.

Lightning web components:
Work inside of communities and portals.
Explore the Digital Experience Layer Unit | Salesforce Trailhead

Manage Signed Documents with OmniScripts
You can create dynamic documents from templates (MS Word, PDF, and HTML outputs), merge data from any data source (for example, Salesforce objects, or user inputs such as sales quotes, order forms, and contracts), and then create and operate on these documents within OmniScripts.
Learn the Fundamentals of OmniScripts Unit | Salesforce Trailhead

When reading a Calculation Procedure, it’s important to know its five basic components, outlined here.
Required:
Variables and Constants: Used in calculation steps
Optional:
Calculation Steps: Matrix and Lookup
Aggregation Steps: Allow you to use data from an array input where the calculations are run on each element separately
Preprocessor Class: Apex classes used to manipulate the input of the calculation
Postprocessor Class: Apex classes used to manipulate the output of the calculation
Perform Complex Math with Calculation Procedures Unit | Salesforce

Use OmniScripts on Any Device and Any Channel
OmniScripts are not restricted to OmniStudio Interaction Consoles for agents to use. You can deploy them on any device and any channel, such as a mobile device, or a consumer portal. Here’s what an OmniScript looks like when viewed on a mobile device and online.
Learn the Fundamentals of OmniScripts Unit | Salesforce Trailhead

FlexCard names cannot be changed. You must clone a FlexCard to change the name.

When you need to access and transform data from third-party sources and no user interaction is required, and when moving the workload from client to server is desirable, then that‘s when you want to use an OmniStudio Integration Procedure.
Get Started with OmniStudio Integration Procedures Unit | Salesforce

Display Data and Actions on a FlexCard Unit | Salesforce Trailhead

Integration Procedure Elements
You might be familiar with using elements in OmniScripts and OmniStudio FlexCards. Integration Procedure elements are a little different. They work behind the scenes—there are no elements for user interaction.
Explore the Integration Procedure Designer Unit | Salesforce Trailhead

There are three types of Calculation Matrices, and their uses vary.
Standard Calculation Matrix: Used when your matrix doesn‘t need to be a part of a group or versioned row by row.
Grouped Calculation Matrix: Used to group similar matrices with the same Input and Output headers together.
Row-Versioned Calculation Matrix: Used if you have a matrix with many rows and may need to change small portions of the data at a time. Each row has its own start date and time

From the following options, indicate which type of datasource you would like to use.
None
SOQL Query
Use the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information.
SOSL Search
Use the Salesforce Object Search Language (SOSL) to construct text-based search queries against the search index.
Apex Remote
Apex Remote data source is used to make a Apex Remote call.
Apex REST
Apex REST data source is used to make a Apex REST call.
DataRaptor
DataRaptor data source is used to make calls to Vlocity DataRaptors.
REST
Uses the standard REST API call.
Integration Procedures
Integration Procedure data source is used to make calls to Vlocity Integration Procedures.
Streaming API
Streaming API enables streaming of events using push technology and provides a subscription mechanism for receiving events in near real time.
Custom
Uses the sample JSON provided.

If there are multiple versions of a matrix, only one version can be accessed at a time, based on these factors:The date/time range on the matrices. (That is, are they active at the same time?)If they are both active, the highest priority active matrix is the one that runs. (1 is the lowest priority.)
The enabled checkbox at the top of the matrix record must be ticked for a matrix to be accessed.

The Service Management layer of OmniStudio includes data services that read, write, transform, calculate, and track data within and outside of Salesforce.
Use the Service Management Layer Unit | Salesforce Trailhead

Embed FlexCards in Other FlexCards
You can embed FlexCards in other FlexCards using the child FlexCard element. You can also launch a child FlexCard from an action element.
Embedding a child FlexCard lets you have multiple data sources within one FlexCard. There’s no limit to how many child FlexCards you can embed; they only need to be active

Fields is in the Build panel.
The style panel is made up of these sections:
Alignment
Update the padding, margin, and text alignment of an element.
Appearance
Configure the color, background, and border of an element.
Custom
Create and apply custom classes, and add inline styles to an element.
Custom CSS
Save style settings on a FlexCard element as a custom style to use on multiple elements of a FlexCard.
Dimensions
Set the height and width, and configure the responsiveness of your element.

What It Is | What It Does
Cache Block | Saves the output of the steps within it to a session or org cache for quick retrieval.
Stores frequently accessed and infrequently updated data, which saves round trips to the database and improves performance
Allows data updates without caching
Allows different cached data to expire at different times
Conditional Block| Executes if a specified condition is true or treats the steps within it as a series of mutually exclusive alternatives
Supports branching workflows, which function like conditional views in an OmniScript
Loop Block | Iterates over the items in a data array, enabling the Actions within it to repeat for each item rather than requiring separate Action elements for each item
Try-Catch Block | Lets you “try” running the steps inside the block and then “catch” the error if a step fails
https://trailhead.salesforce.com/content/learn/modules/omnistudio-integration-procedures/explore-omnistudio-integration-procedure-designer?trail_id=get-to-know-omnistudio

Properties Panel
Configure properties for action, display, function, group, input, and embeddable OmniScript elements in the user interface (UI), or edit properties as JavaScript Object Notation (JSON).

Element Type | What Is It For?
Actions | For calling on other tools to perform various actions: getting or saving data, calculating, sending an email, and so on
Display | For displaying text and images on the screen to enhance the usability of the UI
Functions | For performing calculations within the OmniScript, showing conditional messages, and providing geolocation
Group | For grouping elements together on the UI
Inputs | For system or user input or selection
OmniScripts | Reusable OmniScripts to insert and use

OmniStudio Integration Procedures are applications used to read and write data from Salesforce and from external systems. An Integration Procedure can be called from an OmniStudio component such as an OmniScript or FlexCard, an API, or even from an Apex method.
Get Started with OmniStudio Integration Procedures Unit | Salesforce

Salesforce recommend using Integration Procedures as much as possible as a data source because they have a streamlined structure that’s efficient and consistent. They’re adaptable to use with all your data sources and easy to navigate.
But that’s not all—they give developers a lot more control over the data going back and forth and:
Provide optimal flexibility.
Make implementations easier.
Greatly improve the performance of FlexCards and OmniScripts.
Get Started with OmniStudio Integration Procedures Unit | Salesforce

The input to a Calculation Procedure must be on a JSON node called input with a lowercase i.
OmniStudio_Perform_Complex_Math_with_Calculation_Procedures.pdf (salesforce.com)

All blocks have one property in common—an Execution Conditional Formula.
If this formula evaluates to true or is not defined, the block is executed.
If it evaluates to false, the block is skipped.
Explore the Integration Procedure Designer Unit | Salesforce Trailhead

Use the Service Management Layer Unit | Salesforce Trailhead

Use the Service Management Layer Unit | Salesforce Trailhead

Element Type | What Is It For?
Actions | For calling on other tools to perform various actions: getting or saving data, calculating, sending an email, and so on
Display | For displaying text and images on the screen to enhance the usability of the UI
Functions | For performing calculations within the OmniScript, showing conditional messages, and providing geolocation
Group | For grouping elements together on the UI
Inputs | For system or user input or selection
OmniScripts | Reusable OmniScripts to insert and use