Free SAP Certified Associate - SAP Fiori Application Developer C_FIORD_2502 Exam Questions

The criticality property in @UI.lineItem enables colored status indicators:

Values are interpreted using SAP-defined criticality semantics:

1 = Negative (Red)

2 = Critical (Yellow)

3 = Positive (Green)

SAP Annotations Guide:

''Use criticality in lineItem annotations to enable status coloring for numeric codes representing status.''

Color is not a valid annotation. @UI.selectionField is unrelated to table columns.

Extension points allow app developers to inject custom UI or logic into standard apps:

Custom column: Add additional columns to tables.

Custom section: Extend the Object Page with new sections.

Custom action: Trigger application-specific actions.

Field/Table building blocks are reusable constructs, not extension points per se.

The manifest.json supports various extensibility namespaces:

sap.ui.viewModifications: replaces/changes view content.

sap.ui.controllerExtensions: injects custom logic.

SAP Fiori Extension Documentation:

''The manifest.json file defines UI and logic extensibility using namespaces like viewModifications and controllerExtensions.''

Options B/C are not valid manifest namespaces.

@UI.lineItem specifies table columns in a List Report.

position determines the order of columns: ProductName, Status, Price.

CDS UI LineItem Documentation:

''The lineItem annotation defines columns for tabular display. position is used to sort fields in the UI.''

These are not form fields; they're tabular entries.

SAPUI5 supports different binding types:

Property binding: binds individual attributes (e.g., text='{/name}').

Aggregation binding: binds lists or tables (e.g., items='{/products}').

Element binding: binds a control and its children to a specific path (bindElement('/product')).

SAPUI5 Developer Guide:

''Supported binding types include Property, Aggregation, and Element binding.''

Structure/Combination are not valid SAPUI5 binding categories.

Responsive tables (sap.m.Table) in SAPUI5 use demandPopin, popinDisplay, and screen width qualifiers to optimize mobile display. Correct settings include:

maxScreenWidth='mobile' ensures pop-in on small devices.

demandPopin='true' triggers field reformatting into pop-ins.

popinDisplay='Inline' keeps visual alignment.

SAPUI5 SDK -- Responsive Table Control:

''Use demandPopin with maxScreenWidth and popinDisplay to handle narrow screen layouts.''

Options with minScreenWidth do not apply to mobile-focused pop-in logic.

The sap.m.FacetFilter control fires:

confirm: when filters are applied.

reset: when the user clears filters.

SAPUI5 API Reference - FacetFilter: ''Events include 'confirm', 'reset', triggered by user interactions.''

listFilter/oninit are not defined FacetFilter events.

In a hub deployment:

UI5 app code (HTML/CSS/JS) is deployed on SAP Front-End Server (FES).

Business logic (OData services) remains on Back-End Server (BES).

SAP Fiori Deployment Guide:

''FES hosts the UI components and handles UI5 resource loading. BES contains the application data logic.''

Web Dispatcher only routes traffic. XS Engine is for HANA-native apps.

To build a Worklist-style app using SAP Fiori elements:

Use Application Generator to select List Report and modify it.

In the manifest.json, modify routing and filter bar settings.

Use @UI.hideFilterBar: true annotation in the backend CDS view to suppress the filter bar.

SAP Fiori Elements Implementation Guide: ''@UI.hideFilterBar is used to hide the SmartFilterBar if a minimal worklist-style view is intended.''

OData V4 offers:

Advanced analytical capabilities: including grouping and aggregation.

Improved data types: such as more precise decimal handling.

Flexible Programming Model: thanks to updated APIs and features.

While V4 enables a better technical foundation, UX consistency and compression improvements are not explicitly advantages of V4 over V2.