Pass the SAP Certified Associate C_FIORD_2502 Questions and answers with ExamsMirror

The #COLLECTION type with parentId defines:

Asection("Personal data") containing asubsection("address").

FieldGroup address contains fields like Street and City.

SAP CDS Facet Documentation:

“Use type: #COLLECTION with nested FIELDGROUP_REFERENCE to define section/subsection hierarchies.”

It doesn’t split into two separate sections in the body or header.

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.

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

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.

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.

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.

Flexible Column Layout is a feature that supports responsive design. Configuration can be done via:

manifest.jsonunder the sap.ui5/routing/config section.

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.

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.

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.