SAP C_FIORD_2502 Exam Dumps

SAP Business Application Studio (BAS) provides:

Extensibility Pane: lists available extension points from the standard app.

Wizards: generate required files (e.g., controller extensions, views) automatically.

SAP BAS Guide:

''The Extensibility Pane visualizes available hooks... wizards create necessary files for view/controller/fragment replacement.''

Descriptor editor is used for manifest edits but doesn't directly choose extension elements.

Fragments are XML/JS/HTML code snippets:

They are lightweight and reusable (dialogs, table columns, etc.).

Are loaded via module loader (sap.ui.require) and inserted into views.

SAPUI5 Fragments Documentation:

''Fragments are not self-contained views and do not have controllers. They are loaded by name using module loading.''

A/B are incorrect because fragments lack controller context and cannot act standalone.

Tiles are linked via Target Mappings, which define:

Semantic object + Action combination.

This routing determines what app or view is launched.

SAP Fiori Launchpad Configuration Guide:

''Target mappings define navigation logic using semantic object/action. Tiles use these to determine routing targets.''

Semantic object alone is not actionable.

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.

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.