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?