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

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.

Thei18n.propertiesfile holds thetranslation keys and valuesfor different languages. Demonstrating localization involves:

Showing these files with translations like i18n_fr.properties or i18n_de.properties.

SAPUI5 dynamically picks the language based on browser settings.

SAPUI5 Localization Guide:

“Translation values are maintained in i18n.properties files. The framework selects the appropriate version based on the user’s language preference.”

The other choices (e.g., preview frame or project.json) don’t expose actual translation content.

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.

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

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.

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.

SAP Cloud Connectorcreates areverse-invoke connectionfrom on-premise to BTP and secures communication through anSSL tunnel.

SAP BTP Connectivity Guide:“Cloud Connector creates secure reverse-proxy connections initiated from the on-premise system using HTTPS tunnel.”

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

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.

Fragmentsare XML/JS/HTML code snippets:

They arelightweight and reusable(dialogs, table columns, etc.).

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

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.

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.

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

Generic actionsin SAP Fiori elements include:

Create: enabled by entity-level metadata (CreateAllowed).

Navigation: defined via semantic object and annotation metadata.

SAP Fiori Elements Functional Scope:

“Out-of-the-box actions include Create, Delete, and Navigation depending on metadata. Approve is domain-specific.”

Approve is custom logic and must be implemented manually.

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.