SAP Fiori Application Developer (C_FIORD) Practice Exam

Correct: B — Dependencies, referenced data sources, and app ID, name and version. The app descriptor declares what the app needs and what it is — metadata and configuration — rather than containing the code or content itself.

Why not the others: rendered HTML and CSS (A) are produced at runtime from views and themes; compiled bundles (C) are build output rather than descriptor entries; and controller source and credentials (D) belong in code and platform configuration, never in a descriptor.

Correct: A — No multi-page testing, and end-to-end tests are not recommended. OPA5 is an integration-test framework scoped to the app’s own UI; knowing where it stops is what the question tests, and it is why end-to-end coverage needs a different tool.

Why not the others: never failing (B) would make the framework pointless; requiring a deployed backend (C) contradicts the mock-server pattern OPA5 is usually run with; and replacing QUnit (D) confuses integration tests with unit tests — SAP names both.

Correct: C — It connects BTP services with on-premise systems in the customer’s network. It works by a reverse-invoke process initiated from the on-premise side and secures an SSL tunnel — which is why no inbound firewall opening is needed.

Why not the others: Git connectivity (A) and offline compilation (D) are development-tooling concerns; and listing search components (B) describes app configuration rather than a connectivity component.

Correct: C — Cross-app navigation, with targets deployable separately. Navigating to an intent rather than a URL is what decouples the calling app from the target, so apps can be developed and deployed in parallel and resolved at runtime.

Why not the others: removing target mappings (A) inverts the mechanism, since mappings are how intents resolve; single-transport deployment and build-time resolution (B) describe the coupling intents remove; and guaranteed availability with no authorization checks (D) is simply false.

Correct: D — Annotation file, CDS view, app descriptor, or metadata extension. Fiori elements builds the UI from metadata, and that metadata can be contributed at several layers — which is exactly why the exam asks where, not whether.

Why not the others: the database table (A) holds data rather than UI semantics; the controller at runtime (B) is the freestyle approach Fiori elements avoids; and the launchpad tile (C) governs how an app is launched, not how its page is generated.

Correct: A — The Front-End Server. That separation is the definition of a hub deployment: UI code on the front-end server, business data and logic on the back-end — which is what lets one FES serve several back-ends.

Why not the others: the back-end server (B) holds the business logic and OData services the app calls; the Web Dispatcher (C) routes requests rather than storing code; and the HANA XS engine (D) is a different runtime entirely.

Correct: B — sap.ui.controllerExtensions and sap.ui.viewModifications. Extensions are declared in the descriptor and layered over the standard app, which is what keeps the original untouched and upgrade-safe.

Why not the others: the property names in the remaining options do not exist — they are plausible-sounding inventions, which is precisely how this question separates people who have written an extension from people who have read about one.

Correct: D — Provides both parameters and return values. A stub stands in for a real collaborator on both sides of the call, which is what lets a unit test isolate the code under test from its dependencies.

Why not the others: verifying that methods are called (A) describes a mock or spy rather than a stub; and supplying only parameters (B) or only return values (C) each describe half of what a stub does.

Correct: A — Store tiles and target mappings by technology per solution area, and serve as a reference for business catalogs. Technical catalogs are the inventory; business catalogs reference them and are what get assigned by role — two layers, two purposes.

Why not the others: segregation of duties and role assignment (B) describe business catalogs and roles; grouping for a user role and theming (C) mixes groups with theme configuration; and defining services or storing app code (D) is not what a catalog does.

Correct: B — To understand user needs. The Problem Space exists to establish what users actually need before anyone proposes anything; that is the whole point of separating it from the Solution Space.

Why not the others: validating ideas (A) and creating desirable solutions (C) are Solution Space activities that depend on the understanding the Problem Space produces; and cost saving (D) may follow, but it is a consequence rather than the purpose.