Free Practice Questions for SAP C_FIORD_2502 Exam

SAPUI5 supports differentbinding 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.

To build aWorklist-style app using SAP Fiori elements:

UseApplication Generatorto select List Report and modify it.

In themanifest.json, modify routing and filter bar settings.

Use @UI.hideFilterBar: true annotation in thebackend CDS viewto 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.”

SAP Fiori elements supports extensibility through standardized extension points. These include:

Building Blocks: Reusable content blocks that provide structure and function.

Custom Page Templates: Offered via SAP Fiori tools' application generator to build entire new views.

Thecriticalityproperty in @UI.lineItem enablescolored 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.

SAP Fiori Tools Extension Packallows:

Application generation using Fiori elements templates.

Adding annotations, page maps, and previews.

SAP Fiori Tools Guide:“The Extension Pack enables rapid development of SAP Fiori elements applications via template-based generators and page maps.”

StandardSAPUI5 controller lifecycle eventsinclude:

onInit()

onAfterRendering(): triggered after the view is rendered.

onExit(): when the controller is destroyed.

SAPUI5 SDK - Controller Lifecycle:

“Use onAfterRendering to manipulate HTML elements. Use onExit for cleanup operations.”

Options A and B are not standard lifecycle hooks.

ODataModelis the only model that:

Supportsdeep inserts, i.e., inserting parent and child entities in one request.

Utilizesnavigation propertiesand the $expand functionality.

SAP Gateway Developer Guide:

“A deep insert involves a POST request with a nested payload… supported only by the OData model.”

XML/JSON/Resource models are static and client-only, without support for backend communication or nested entity posting.

manifest.json:

Describes the application structure, routing, models, and resources.

Acts as the central metadata descriptor.

SAPUI5 SDK:

“The manifest.json is the application descriptor containing metadata for deployment, models, routing, and UI configuration.”

Component.js bootstraps the app, but manifest.json holds app metadata.