The correct approach is to rely on OmniScript's standard responsive layout behavior instead of manually hard- coding field widths or replacing the entire layout with custom Lightning web components. OmniScript designers support previewing scripts across device form factors such as Mobile, Tablet, and Desktop, and element display properties are intended to support responsive behavior. Manual width settings and custom media-query CSS should be reserved for exceptional branding or layout needs because they increase maintenance burden and can conflict with framework behavior. A custom LWC for the full layout would be excessive and would bypass much of OmniScript's declarative value. Since the requirement is that input fields adjust correctly on smaller screens, the standard responsive OmniScript layout is the best-supported answer.

A FlexCard is the correct user-interface component for displaying summarized, contextual, responsive information from one or more data sources. The scenario is not asking for a guided form or step-by-step process; it asks for a single-page health summary with list-like lab results and interactive display behavior. An Integration Procedure can absolutely be used behind the FlexCard to aggregate Salesforce demographic data and EMR lab results, but the component that displays and manages the responsive interaction is the FlexCard.
A Data Mapper Extract only retrieves Salesforce data and does not handle external EMR data or UI interaction. OmniScript is better for guided data collection and process automation, not a compact summary card. Therefore, the front-end OmniStudio component should be a FlexCard.

To build and modify OmniStudio components, the user needs both entitlement to OmniStudio features and permissions to create or manage the designer artifacts. The OmniStudio User permission set license provides access to OmniStudio features and objects, while the OmniStudio Admin permission set grants administrator
/developer-level access to create and manage OmniScripts, FlexCards, Integration Procedures, and Data Mappers. A Salesforce platform license alone is not enough because it does not automatically expose OmniStudio designers. Option D is wrong because "OmniStudio Developer permission set" is not the standard answer in this context. Options B and C incorrectly rely on an Admin PSL combination rather than the common OmniStudio User PSL plus Admin permission set pairing. Salesforce's OmniStudio permission guidance supports assigning OmniStudio Admin permissions for users who need to work with the designers.

In OmniStudio, the Edit Block element is purpose-built for allowing users to dynamically add, edit, or delete rows of related data, such as dependents under a policy. To save these changes, Remote Actions (typically backed by Apex or API) are used to process each record operation (Create/Update/Delete).
* A. Use an Edit Block element configured with Remote Actions - Correct. This is the recommended and most scalable way to support CRUD operations in OmniScripts for collections (e.g., dependents). The Edit Block provides UI-level support, while Remote Actions handle back-end interaction with Salesforce or external systems.
Incorrect Options:
* B. Text Block is for display purposes and cannot manage data input or backend actions.
* C. Input Block elements do not support row-level add/edit/delete functionality as Edit Blocks do.
* D. SOQL is a read-only query language and cannot be used to update or delete records directly within an OmniScript.
Salesforce OmniStudio Guide # OmniScript Edit Block Element
OmniStudio Best Practices # CRUD Operations in OmniScripts

According to the Integration Procedure Actions page, a Calculation Action can be used to "call a Calculation Procedure that performs calculations on input data" and a Matrix Action can be used to "call a Calculation Matrix that performs calculations on input data".