SAP C_FIORD_2502 SAP Certified Associate - SAP Fiori Application Developer Exam Practice Test

manifest.jsonis the application descriptor in SAPUI5 apps. It defines routing, models, UI configuration, and more.

Other files are irrelevant for core Fiori elements configuration.

On theObject Page Header:

title.valuedisplays actual value of field Sales order Number.

description.valueshowsSales Order Ownertext.

SAP CDS Annotations Guide:

“In object pages, headerInfo.title.value and description.value are displayed prominently in the page header.”

TypeName/Plural are used for page titles and breadcrumbs.

To add afilter field, use:

UI.SelectionFieldannotation in the CDS view.

In QUnit:

TheActis the operation you’re testing — in this case, pressing a button (press("1")).

Arrangeis setting up the object.

Assertis comparing the output.

QUnit Testing Concepts:

“Act corresponds to executing the logic you want to test (e.g., method calls).”

SAP Fiori elements support rendering of:

Micro Chartsusing @UI.chart inside table columns.

Imageswith appropriate annotations or formatter logic.

Text, the default for most line item entries.Charts and nested tables are not rendered inside cells.

SAP Fiori Elements Developer Extensibility Guide:“Micro charts can be embedded in cells… Images and formatted text are supported.”

Fact Sheet appsare designed to be launched viaEnterprise Searchin the Fiori Launchpad:

Tied to asemantic objectand accessed from search results.

Show detailed object data in a drill-down format.

SAP Fiori App Types Guide:

“Fact Sheet apps are integrated into the Enterprise Search and typically launched from search results, not from tiles.”

Transactional and analytical apps are primarily accessed via tiles or navigation.

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.

Thesap.m.FacetFiltercontrol 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.

SAPUI5 supports three maindata binding modes:

One-way: Data flows from model to view.

Two-way: Data syncs both directions (used in forms).

One-time: Data is injected once and not updated.

SAPUI5 Developer Guide:

“Binding modes define how data is synchronized between the model and the view. The supported modes are: OneWay, TwoWay, OneTime.”

Three-way and resource-model binding are invalid or unrelated to binding modes.

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.

Building blocksare UI components that simplify layout composition:

InPFCG, to authorize access to Fiori apps:

Assign thecatalogto theMenu tabof a role.

The user must be assigned the role.

SAP Authorization Guide:

“Fiori Catalogs must be added in the PFCG Menu tab to include corresponding apps in user authorization.”

Authorization tabs are used for backend authorizations, not app tiles.

In OData:

POSTis used tocreatenew entities.

PUTandPATCHare used to update existing entities.

CHANGE and UPDATE are invalid HTTP methods.

SAP OData V2/V4 Protocol Guide:

“To create a new entity, a POST request is issued to the entity set URL with the new entity’s payload.”

TheODataModelsupports data binding to back-end OData services and includes fullserver-side capabilities:

Sorting,filtering,paging, andbatchingare natively processed by the server via query options ($orderby, $filter).

This offloads processing from the client and ensures efficient data handling.

SAPUI5 SDK - ODataModel (v2andv4):

“The ODataModel provides advanced features like server-side sorting and filtering using standard OData query options.”

In contrast, JSONModel, ResourceModel, and XMLModel are client-only and lack these features.

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 offersmultiple extension mechanisms:

Adaptation Project: customizes standard apps without copying code.

View Extensions: via manifest.json to inject custom UI at extension points.

Controller Hooks and Property Overridesfor fine-grained control.

SAP Fiori Extensibility Guide:

“Adaptation projects allow for UI and logic customization using SAP Business Application Studio.”

Changing runtime libraries or merging data at runtime are neither recommended nor supported directly.

SAPUI5 supportslocalization via resource bundles:

.properties files (often mistakenly called .props) are used for language-specific translations.

One default file (i18n.properties) and additional ones like i18n_fr.properties.

These files containkey-valuepairs for translation.

SAPUI5 SDK:

“Internationalization is supported using resource bundles. Each bundle is a .properties file with keys and translations. You must provide separate files per language.”

Creating separate views/controllers per language is incorrect; views are static. HTML character encoding is optional and not specific to language support.

Pushsends local Git commits to a remote repository.

Commitstores changes locally.

Pushshares them remotely.

SAP BAS Git Integration Guide:“Push moves the committed local changes to the corresponding remote branch.”