SAPUI5 & SAP Fiori Elements

Which SAP runtimes ship SAPUI5 automatically (so you don't deploy the framework separately)?

You're choosing a data source for a new SAPUI5 app against an SAP back end. Why does SAP steer you to SAP Gateway (OData) rather than a plain JSON/XML feed, and what do you lose if you go JSON?

A stakeholder asks why the Overview Page uses 'cards' instead of just a launchpad of tiles. What does a card actually deliver that a launch tile doesn't?

In a SAPUI5 MVC app, a developer puts UI-formatting logic into the Model 'to keep it close to the data.' Why is that the wrong layer, and where does that logic belong?

A developer says a screen uses 'two-way' binding so 'the model and the view stay in sync.' What does two-way binding actually guarantee, and what does it NOT mean?

On an Overview Page you need to surface several individual objects, each with its own detail view, that the user pages through — and let them jump either to the parent app or to the object stream. Which of the five card types fits, and how is it different from a List card?

SAPUI5 lets you define a view four ways. For a standard declarative, maintainable, tooling-friendly Fiori UI, which do you reach for — and which would you only pick when you need programmatic control at runtime?

Among the four SAPUI5 bootstrap parameters, which one is about surviving framework upgrades — and what does leaving it unset expose you to?

The render manager creates the HTML for controls. Does it live in the SAPUI5 library or the core — and why does that placement make sense?

What are the two build steps to create an Overview Page app and add a card to it in the project wizard?

A requirement says 'let the user display, create, or edit a single item as a 360° view.' Which Fiori floorplan is that — and which classic S/4HANA app type did it replace?

You need a screen where users browse, filter, and act on a large set of items. Which Fiori floorplan, and what is the one thing it must let users do that a plain read-only table doesn't?

A Fiori elements app renders the wrong columns / missing sections, and a developer starts editing the floorplan template. Why is the annotation file the more likely fix?

A colleague says 'we'll build this in SAP Fiori, not SAPUI5.' Why is that a category error?

Two teams build the same app: one with freestyle SAPUI5, one with SAP Fiori elements. What does the Fiori-elements team get that the freestyle team must hand-build, and what are the two ingredients that make it work?

Before any SAPUI5 control can run, the framework has to be present. What single piece of markup loads it, and where does it live?