What are characteristics of SAP HANA modelling in XS Advanced? Note: There are 2 correct answers to this question

Question

Options

• AUse of SAP HANA Studio as a user interface
• BPotential use of GitHub as a source code repository
• CImport of SAP HANA HDI Calculation View as a file in a project
• DDeployment of external SAP HANA views generated from BW objects

• A
  4% (1)
• B
  87% (20)
• D
  9% (2)

Explanation

In XS Advanced (XSA), development follows a modern, Git-based workflow using the SAP Web IDE for SAP HANA (browser-based), which natively supports connecting to Git repositories - including GitHub - for version control and collaboration, making B correct. XSA also uses the HDI (HANA Deployment Infrastructure) container model where artifacts like Calculation Views are represented as files (e.g., .hdbcalculationview) within a project structure and can be imported as such, making C correct.

A is wrong because SAP HANA Studio is associated with the older XS Classic environment; XSA replaced it with the browser-based Web IDE. D is wrong because deploying external views generated from BW objects is a BW-on-HANA/BW4HANA concept, not a characteristic of XSA modelling itself.

Memory tip: Think "XSA = modern development" - it ditched the desktop tool (Studio) in favor of a browser IDE with Git support, and everything in a project is a file, including Calculation Views. If an answer sounds like "old school HANA" or "external BW integration," it's likely a distractor.

No community discussion yet for this question.