StandardSAPUI5 controller lifecycle eventsinclude:

onInit()

onAfterRendering(): triggered after the view is rendered.

onExit(): when the controller is destroyed.

SAPUI5 SDK - Controller Lifecycle:

“Use onAfterRendering to manipulate HTML elements. Use onExit for cleanup operations.”

Options A and B are not standard lifecycle hooks.

To add afilter field, use:

UI.SelectionFieldannotation in the CDS view.

SAP Fiori elements supports extensibility through standardized extension points. These include:

Building Blocks: Reusable content blocks that provide structure and function.

Custom Page Templates: Offered via SAP Fiori tools' application generator to build entire new views.

Building blocksare UI components that simplify layout composition:

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.

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.

SAPUI5 supports three maindata binding modes:

One-way: Data flows from model to view.

Two-way: Data syncs both directions (used in forms).

One-time: Data is injected once and not updated.

SAPUI5 Developer Guide:

“Binding modes define how data is synchronized between the model and the view. The supported modes are: OneWay, TwoWay, OneTime.”

Three-way and resource-model binding are invalid or unrelated to binding modes.

Deployment Targetsfor SAPUI5 apps from BAS include:

SAP BTP(via HTML5 App Repository or MTA).

SAPUI5 ABAP Repositoryon an on-premise or S/4HANA backend system.

SAP Deployment Guide:

“Deployment to ABAP repository or HTML5 App Repository on SAP BTP is supported. SAPUI5 Java repo is deprecated.”

Fiori Launchpad is not a deployment target but a UI layer.

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.

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.

SAPUI5 supports differentbinding types:

Property binding: binds individual attributes (e.g., text="{/name}").

Aggregation binding: binds lists or tables (e.g., items="{/products}").

Element binding: binds a control and its children to a specific path (bindElement("/product")).

SAPUI5 Developer Guide:

“Supported binding types include Property, Aggregation, and Element binding.”

Structure/Combination are not valid SAPUI5 binding categories.