C_FIORD_2502 Exam Dumps - SAP Certified Associate Questions and Answers

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

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.

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.

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.

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.

InPFCG, to authorize access to Fiori apps:

Assign thecatalogto theMenu tabof a role.

The user must be assigned the role.

SAP Authorization Guide:

“Fiori Catalogs must be added in the PFCG Menu tab to include corresponding apps in user authorization.”

Authorization tabs are used for backend authorizations, not app tiles.

Tile visibility in Fiori Launchpad depends on:

Target Mappingsbeing defined.

The tile being part of aGroupassigned to the user.

OData service authorizationsbeing present (no access = no launch).

SAP Fiori Launchpad Troubleshooting Guide:

“Missing target mapping, group, or backend authorization will prevent tile visibility even if the catalog is assigned.”

PFCG and catalog issues alone won't prevent the App Finder from showing all apps.

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.