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

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.

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.

ResponsiveFlowLayoutallows content towrap and flowaccording to screen size and available space:

Preferred for building responsive UI layoutswithout tables.

Supports multiple rows and automatic adjustment of elements.

SAPUI5 Layout Control Reference:

“ResponsiveFlowLayout arranges controls in rows, wrapping them depending on the available width.”

Grid layout is rigid, and Vertical/Horizontal layouts are not responsive.

SAP Fiori Tools Extension Packallows:

Application generation using Fiori elements templates.

Adding annotations, page maps, and previews.

SAP Fiori Tools Guide:“The Extension Pack enables rapid development of SAP Fiori elements applications via template-based generators and page maps.”

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.

StandardSAPUI5 controller lifecycle eventsinclude:

onInit()

onAfterRendering(): triggered after the view is rendered.

onExit(): when the controller is destroyed.

SAPUI5 SDK - Controller Lifecycle:

“Use onAfterRendering to manipulate HTML elements. Use onExit for cleanup operations.”

Options A and B are not standard lifecycle hooks.

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.

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.

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

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.

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

Groupsare optional in SAP Fiori 3 and newer versions:

Used tovisually organize tiles.

Tiles/apps can still be accessed via theApp Finderif the catalog is assigned.

SAP Fiori Launchpad Admin Guide:

“Groups are optional. Users can use App Finder to launch apps directly from catalogs.”

Other steps like creating catalogs and target mappings are essential for app accessibility.

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.

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

OData V4 offers:

Advanced analytical capabilities: including grouping and aggregation.

Improved data types: such as more precise decimal handling.

assert.strictEqual() checks bothvalue and typeusingstrict equality (===)in JavaScript.

0 === -0 →true

Others fail due to type mismatch or value mismatch.

QUnit API Reference:

“Use strictEqual for strict equality. It compares both value and type.”

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.

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.