Your company decided to use a Hadoop cluster as a data storage location. Which components can be used to consume remote Hadoop data in your SAP HANA native app? (3)

Question

Options

• ASAP HANA smart data access
• BSAP HANA smart data integration
• CSAP HANA SQL controller
• DSpark SQL adapter
• ESAP Vora ODBC adapter

• A
  88% (23)
• B
  4% (1)
• C
  8% (2)

Explanation

SAP HANA Smart Data Access (A) provides the federation framework that lets HANA query remote Hadoop data via virtual tables without moving it. The Spark SQL adapter (D) plugs into SDA specifically to translate HANA queries into Spark SQL for execution on a Hadoop cluster. The SAP Vora ODBC adapter (E) connects HANA to SAP Vora - a Hadoop-native SQL engine - allowing HANA native apps to query data stored there via ODBC.

B (Smart Data Integration) is wrong because SDI is an ETL/replication tool (it moves or transforms data using a Data Provisioning Agent), not a remote consumption/federation mechanism - the distinction is "replicate" vs. "access in place." C (SAP HANA SQL Controller) is a fabricated distractor; no such component exists in the SAP HANA product suite.

Memory tip: Think "A-D-E = Access Data Externally" - all three are about reaching out to Hadoop and consuming it in place (SDA as the framework, Spark SQL as the Hadoop adapter, Vora ODBC as the Hadoop-native SQL bridge), while SDI is the odd one out because it pulls data in rather than consuming it remotely.

No community discussion yet for this question.