C_FIORD_2502 SAP Certified Associate - SAP Fiori Application Developer Questions and Answers

TheOverview Page (OVP)template uses cards to visualize key metrics, charts, and actionable insights. It's designed to aggregate and highlight information from multiple sources.

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.

In ahub deployment:

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

Business logic (OData services) remains onBack-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.

@UI.lineItem specifiestable columnsin a List Report.

position determines theorderof 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.

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.

Tiles are linked viaTarget Mappings, which define:

Semantic object + Actioncombination.

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.

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.

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

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.

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.

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.

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.

OPA5 (One Page Acceptance)testing framework is used for:

End-to-end integration testingof SAPUI5 apps.

Verifyingnavigation, routing, and view transitionsusing test cases written in Given-When-Then format.

SAPUI5 Testing Guide:

“OPA tests simulate full user interactions, including navigation, and validate that applications behave as expected.”

QUnit is for unit tests. Sinon is a mocking library. Mock server simulates backend but doesn’t test navigation logic.

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.

View Replacementis the most invasive extensibility technique used when extension points aren’t sufficient. It includes:

Building a completely newXML viewand mapping it via sap.ui.viewReplacements in the manifest.

Assessmentthat the available extension hooks (like controller or fragment replacements) don’t fulfill the requirement.

SAP Extensibility Guide:

“Use view replacement only if the application cannot be extended via extension points or controller hooks.”

Replacing individual controls (C, D) aligns more withcontrol replacement, not full view substitution.