C_FIORD_2502 SAP Certified Associate - SAP Fiori Application Developer Free Practice Exam Questions (2025 Updated)

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.

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.

typeNamePlural defines thetable titlein list report pages.

In this case: Sales Orders.

SAP Annotations Reference:

“The typeNamePlural is rendered as the title of the List Report table.”

The title and description fields affect object pages and record headers, not the list title.

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.

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.

MVCarchitecture separates concerns:

Modelhandles data.

Viewdisplays data.

Controllerhandles logic.

Advantages:

Views can be changedindependently from business logic (Controller).

Multipleviewscan present the same model data differently.

SAP MVC Documentation:

“MVC enables separation of concerns, easier debugging, and reusability of components.”

Quick coding is not inherently a feature of MVC, and transport independence is handled via SAP tooling, not MVC itself.

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.

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.”

Building blocksare UI components that simplify layout composition:

The manifest.json supports variousextensibility 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.

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.

SAPUI5 SDKprovides:

ExtensiveUI controls(charts, tables, lists, dialogs, etc.)

Internationalization (i18n)support for multi-language development.

SAPUI5 SDK Features Overview:

“SAPUI5 offers a responsive design across all devices and full translation support via resource bundles.”

Web Dynpro is unrelated; responsiveness is not limited to non-mobile devices.

Given the hierarchical structure, where regions is an array, and companies is a sub-array under region[0], correct access is:

/regions/0/companies: path to company list in first region (Americas).

name and city are properties of each company.

SAPUI5 Model Binding Guide:

“To bind list data in nested arrays, use full path access like /parent/0/child.”

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.

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.”

OData Model Editorin SAP Business Application Studio supports:

Creatingnew OData V4/V2 models using visual tools.

Editingentity sets, associations, and annotations.

SAP BAS Documentation:“The Model Editor enables creation and modification of metadata files for OData services.”

Testing and deployment are handled externally.

QUnitfollows theAAApattern:

Arrange: Prepare test data/setup.

Act: Perform the operation.

Assert: Validate the result.

SAP Testing Guidelines:

“The Arrange-Act-Assert (AAA) pattern is fundamental to unit testing logic with QUnit.”

B is the pattern for OPA5 (behavioral testing), not QUnit.