E_HANAAW_14 ABAP for SAP HANA

Question

Which of the following SAP HANA-Based scenarios involve ABAP Applications? - HA400 - Unit 1/Less_1. Pg. 5,6.

Answer 1

Data Smart Based on SAP HANA.

Answer 2

AS ABAP with SAP HANA as primary database.

Answer 3

Native SAP HANA Applications.

Answer 4

SAP HANA as Business Acelerators.

Answer 5

Instance Number

Answer 6

Cliente ID

Answer 7

Logon Language

Answer 8

Calculation View

Answer 9

External Views

Answer 10

Database Procedure Proxy

Answer 11

ABAP-Manage Database Procedure

Answer 12

Use of native QSL or DB Hints.

Answer 13

Use of secondary database connection.

Answer 14

Coding that assumes that a SELECT result is always sorted.

Answer 15

The existence of customer-specific cluster tables.

Answer 16

The existence of table appends.

Answer 17

In a Code Inspector object list.

Answer 18

In a Code Inspector object check variant.

Answer 19

In a Code Inspector inspection.

Answer 20

Use of SELECT.. FOR ALL ENTRIES..

Answer 21

Use of JOINS with more than 3 tables.

Answer 22

Use of SELECT statements in LOOPS.

Answer 23

Use of SELECT * for tables with many fields.

Answer 24

Do static code checks with Code Inspector or ABAP Test Cockpit.

Answer 25

Collect runtime data with SQL Monitor.

Answer 26

Collect runtime data with Runtime Analysis.

Answer 27

Combine runtime data and static check result in SQL Performance Tuning Worklist.

Answer 28

Collect runtime data in the productive system.

Answer 29

Do static SQL checks in the productive system.

Answer 30

Do static SQL check in the development system.

Answer 31

Combine runtime data and static check result.

Answer 32

Keep the result set small.

Answer 33

Minimize amount of transferred data.

Answer 34

Minimize number of database accesses.

Answer 35

Minimize search overhead.

Answer 36

Keep unnecessary load away from the DB.

Answer 37

Keep the result set small.

Answer 38

Minimize amount of transferred data.

Answer 39

Minimize number of database accesses.

Answer 40

Minimize search overhead.

Answer 41

Keep unnecessary load away from the DB.

Answer 42

Translate Open SQL syntax into Native Sql Syntax.

Answer 43

Add client handling to the statement.

Answer 44

Check User Authorizations

Answer 45

Handle SAP table buffering

Answer 46

Transaction handling

Answer 47

Data definition (aka DDL source)

Answer 48

Data Definition ( aka DDL source ).

Answer 49

The Association points to a table, not to another CDS View.

Answer 50

The Association has cardinality 'to N'.

Answer 51

All fields mentioned in the ON condition are part of the field list.

Answer 52

The Association is the only Association in this view definition.

Answer 53

In the Data Preview of ADT.

Answer 54

In the Data Browser ( transaction SE16 ).

Answer 55

In another CDS view

Answer 56

In an Open SQL SELECT statement

Answer 57

In Data preview in ADT.

Answer 58

In the Data Browser ( SE16 ).

Answer 59

In ABAP Open SQL.

Answer 60

In the definition of another CDS view.

Answer 61

In Data preview in ADT.

Answer 62

In the Data Browser ( SE16 ).

Answer 63

In ABAP Open SQL.

Answer 64

In the definition of another CDS view.

Answer 65

Key words are not case-sensitive.

Answer 66

Identical client handling.

Answer 67

Table names have to be upper-case.

Answer 68

Comma-separated field lists.

Answer 69

Field list after FROM clause is supported.

Answer 70

Numeric or character-like scalar types.

Answer 71

Structure types with only scalar components.

Answer 72

Table types with only scalar columns.

Answer 73

Nested table types without secondary keys.

Answer 74

Display an AMDP method implementation.

Answer 75

Edit an AMDP method implementation.

Answer 76

Test an AMDP method implementation.

Answer 77

Debug an AMDP method implementation.

Answer 78

Create an instance of CL_SQL_CONNECTION.

Answer 79

Create an instance of CL_SQL_STATEMENT.

Answer 80

Create an instance of CL_SQL_RESULT_SET.

Answer 81

None, all three are mandatory.

Answer 82

You don’t forget a result.

Answer 83

An exception is raised.

Answer 84

DB resources remain blocked.

Answer 85

FROM _SYS_BIC.“ha400.primdb.::CA_BOOKINGS_COUNT”

Answer 86

FROM “ha400.primdb::CA_BOOKINGS_COUNT”

Answer 87

FROM _SYS_BIC.“ha400.primdb/CA_BOOKINGS_COUNT”

Answer 88

FROM “ha400.primdb/CA_BOOKINGS_COUNT”

Answer 89

Two table-like results.

Answer 90

Two scalar results.

Answer 91

One scalar result.

Answer 92

One table-like result.

Answer 93

Procedure Proxy.

Answer 94

Database View.

Answer 95

External View.

Answer 96

No native SQL required to access the SAP HANA object.

Answer 97

Automatic synchronization of proxy object definition

Answer 98

Automatic transport of SAP HANA artefacts in ABAP transport request.

Answer 99

No need for SAP HANA database to define the proxy objects.

Answer 100

Table TAB is located in column store.

Answer 101

Column COL is of type TEXT or SHORTTEXT.

Answer 102

A full text index exists for column COL of table TAB.

Answer 103

The application server release is 7.40 SP05 or higher.

Answer 104

Transparent table

Answer 105

Database view

Answer 106

External view

Answer 107

Personalization

Answer 108

Editing values

Answer 109

Excel export

Answer 110

Double-click

Answer 111

Increasing connectivity of people and devices

Answer 112

Move transactional processing and analysis to separate servers for better scalability

Answer 113

Increase in use of mobile devices

Answer 114

Massive growth in data volume

Answer 115

Faster disk access.

Answer 116

Multi-core processing.

Answer 117

Larger memory availability.

Answer 118

In-memory database

Answer 119

Automatic compression of data

Answer 120

Removes the need for cache

Answer 121

Combined OLTP and OLAP processing on one platform

Answer 122

SAP HANA runs on Intel x86 and SPARC hardware platforms.

Answer 123

SAP HANA runs on Unix.

Answer 124

SAP HANA can be installed only by certified engineers for production purposes.

Answer 125

Customers can re-use their own certified hardware components in an SAP HANA system.

Answer 126

SAP HANA is available in the cloud or on premise, or a combination of both.

Answer 127

Data cleansing

Answer 128

Data transformation

Answer 129

Data streaming

Answer 130

For data loading

Answer 131

A native, lightweight application server

Answer 132

An optional engine to handle excessive data loads

Answer 133

A data cleansing engine

Answer 134

A user interface

Answer 135

To move to Cloud Foundry architecture to allow flexible application deployment options

Answer 136

To include ABAP as a key development language for native SAP HANA applications

Answer 137

To implement micro-services architecture

Answer 138

To provide better source code management tools inside SAP HANA

Answer 139

Database Explorer

Answer 140

Development

Answer 141

Calculation Views

Answer 142

Analytic Privileges

Answer 143

Procedures

Answer 144

Calculation View

Answer 145

Analytic Privilege

Answer 146

To provide KPIs to help focus on business performance

Answer 147

To provide key system performance information for one or more HANA instances

Answer 148

To provide an application developer collaboration hub

Answer 149

Data footprint is automatically reduced through compression

Answer 150

Only the columns required are actually loaded to memory

Answer 151

Columns can be partitioned

Answer 152

They are optimized for high-volume read/write transactional processing

Answer 153

To store data that has been unloaded from memory

Answer 154

To hold the delta store for newly-arrived records

Answer 155

To enable full database recovery if we have a power failure

Answer 156

To store data that is frequently used

Answer 157

A table that can hold data in row and column orientation

Answer 158

A table that can distribute its partitions across memory and extended storage tiers

Answer 159

A table that can be shared across multiple instances of HANA

Answer 160

An application built with SAP HANA XS Classic (XS) that supports on-premise and cloud deployments

Answer 161

An application built with SAP HANA XS Advanced (XSA) that supports on-premise and cloud deployments

Answer 162

Data volume

Answer 163

Delta store

Answer 164

To push data-intensive processing up to the application to obtain the best performance

Answer 165

To develop reuseable data processing logic in the database

Answer 166

To simplify applications

Answer 167

Cube with star schema

Answer 168

Dimension with star schema

Answer 169

SQL permission

Answer 170

Authorisation object

Answer 171

Analytic privilege

Answer 172

SAP S/4HANA

Answer 173

SAP Business Suite

Answer 174

SAP HANA Live

Answer 175

SAP HANA CDS

Answer 176

To extract the sentiment from customer feedback on social media

Answer 177

To extract common entities such as company, country, currencies, and so on, found in documents

Answer 178

To identify close matches in words and expressions, to catch misspellings

Answer 179

Calculation View

Answer 180

Predictive Analysis Library

Answer 181

A tool to support sizing of an SAP HANA solution

Answer 182

A tool used to define a data loading job

Answer 183

A tool to support the build of a logical data model

Answer 184

A tool used to simulate a work load on different HANA hardware configurations

Answer 185

Virtualization

Answer 186

Duplicate data

Answer 187

Automatic data type translation

Answer 188

Data cleansing

Answer 189

Evaluation and execution of push-down possibilities to remote sources

Answer 190

Merging data from multiple sources

Answer 191

The new table always has a 1:1 mapping between the file and table columns.

Answer 192

The supported file types for upload are .csv, and .txt.

Answer 193

When loading new data in a table that already contains data, the new data is appended to the existing data.

Answer 194

Renaming of columns and changing data types is allowed when loading data to new HANA tables.

Answer 195

Embedded Analytics for operational analytics

Answer 196

ABAP is replaced with JAVA

Answer 197

Combine operational analytics and transaction processing

Answer 198

Massive performance improvement

Answer 199

Optimized for SAP HANA but maintains compatibility with other platforms

Answer 200

Embedded Analytics

Answer 201

Rewritten ABAP code optimized for SAP HANA

Answer 202

SAP HANA Live provides real time operational analytics

Answer 203

Tighter security

Answer 204

Data loading performance

Answer 205

Superior data quality

Answer 206

Reporting performance

Answer 207

Integration of classic BW models such as InfoSets or InfoCubes with SAP HANA Calculation views

Answer 208

Integration of SAP HANA optimized BW models such as ADSOs or OpenODS views with SAP HANA Calculation views

Answer 209

Integration of models from BW on non-HANA databases combined with SAP HANA optimized BW models

Answer 210

SAP HANA Studio

Answer 211

SAP BW/4HANA

Answer 212

SAP HANA Data Warehousing foundation

Answer 213

SAP HANA Web-based Workbench

Answer 214

SAP Web IDE for SAP HANA

Answer 215

SAP HANA Studio

Answer 216

SAP Web IDE

Answer 217

The Eclipse platform is an important part of SAP’s strategy for development tools

Answer 218

The Eclipse IDE is an interesting but non-essential addition

Answer 219

ABAP tools in Eclipse is just a proof of concept for the moment

Answer 220

In the project properties dialog box

Answer 221

Under Window→ Preferences

Answer 222

In both the project properties dialog box and under Window→ Preferences

Answer 223

Transport Organizer

Answer 224

ABAP programs

Answer 225

Data elements

Answer 226

ABAP classes

Answer 227

Text elements

Answer 228

Shift + Enter

Answer 229

Ctrl + Enter

Answer 230

Alt + Enter

Answer 231

Ctrl + Shift + Enter

Answer 232

Setting breakpoints dynamically during debugging

Answer 233

Memory analysis

Answer 234

Source code editing in the debugger

Answer 235

Displaying the contents of an internal table

Answer 236

Use the IMPORTING, EXPORTING, CHANGING, EXCEPTIONS, and RAISING additions in the FUNCTION statement

Answer 237

You can’t - the interface must be edited using the Function Builder in the SAP GUI

Answer 238

Choose the Code Wizard icon from the application toolbar

Answer 239

Choose F2 then choose the required action

Answer 240

Choose Ctrl + Space then choose the required action

Answer 241

Add the implementation of the method

Answer 242

Move the method definition to the protected or private section

Answer 243

Delete the method

Answer 244

Ctrl + Shift + F5

Answer 245

Ctrl + Shift + H

Answer 246

Ctrl + Shift + A

Answer 247

The Code Inspector

Answer 248

The Extended Program Check

Answer 249

The ABAP Trace

Answer 250

Test classes are not generated in a production system

Answer 251

Test methods can access the private components of the class under test

Answer 252

The class under test can access the methods of the test class

Answer 253

Each test method is executed independently of all of the others

Answer 254

Delivery Units.

Answer 255

Calculation Views.

Answer 256

Procedures.

Answer 257

Cube with star join

Answer 258

They do not expose their meta data to reporting tools

Answer 259

They are mainly used for reusing inside other calculation views

Answer 260

They must include at least one measure

Answer 261

They include a star join node

Answer 262

Calculation views

Answer 263

Flat files

Answer 264

Virtual tables

Answer 265

Column tables

Answer 266

Row tables

Answer 267

A view that is only accessible by users for a limited time

Answer 268

A view that stores the values of attributes across time

Answer 269

Excel pivot tables

Answer 270

Custom SQL queries

Answer 271

Data preview function in Web IDE

Answer 272

To apply filters on the data

Answer 273

To extract only the required columns from a data source

Answer 274

To aggregate measures

Answer 275

To join data sources

Answer 276

To improve performance of joins that do not need to check integrity if no column from the right table is selected by a query.

Answer 277

When you need to display only facts that have associated master data attributes

Answer 278

When you want to display facts even when the associated master data attributes are missing.

Answer 279

Left Outer Join

Answer 280

Right Outer Join

Answer 281

Temporal Join

Answer 282

Full Outer Join

Answer 283

Transparent filter

Answer 284

Dynamic join

Answer 285

Cube calculation views

Answer 286

Column tables

Answer 287

Dimensions calculation views

Answer 288

Before a query on the calculation view begin to execute

Answer 289

On the final result of a query, similar to a ‘where’ clause

Answer 290

Before any joins are executed within the calculation view

Answer 291

Attributes

Answer 292

Input parameter

Answer 293

Input parameter

Answer 294

A parent can be formed by combining attributes.

Answer 295

Parent and child columns have the same data type.

Answer 296

Recursive data structure defines the hierarchy.

Answer 297

The hierarchy always generates two levels.

Answer 298

To migrate deprecated object types to the supported types

Answer 299

To access the latest features of calculation view modeling

Answer 300

To maintain attribute and analytic views

Answer 301

To work with a tool you are familiar with when modeling XSA based development objects

Answer 302

So that they can avoid creating calculation views and use SQL

Answer 303

So that they can understand how to implement a function or procedure

Answer 304

So that they can extend the capabilities of a calculation view using SQL expressions

Answer 305

When writing SQL against a database connection of the type HDI Container

Answer 306

When writing SQL against a database connection of the type SAP HANA Database.

Answer 307

As a replacement for a graphical calculation view when you need more flexibility

Answer 308

When you need to write results back to a table

Answer 309

When you need to define custom data processing logic that the graphical calculation view cannot provide

Answer 310

Write your code in a source file in the SAP Web IDE with the extension .hdbprocedure

Answer 311

Use the CREATE PROCEDURE statement in SQL Console

Answer 312

The syntax is much simpler than the standard SQL Create Table expression.

Answer 313

A table that is created with CDS performs better than one created with the standard SQL ‘Create Table’ expression.

Answer 314

The table definition is easily transported as part of the overall application to ensure all artifacts are kept together.

Answer 315

Calculation views of data category cube without star join

Answer 316

Calculation views of data category cube with star join

Answer 317

Calculation views of data category ‘blank’

Answer 318

Calculation views of data category dimension

Answer 319

It provides a quick start to use SAP HANA Live for customers using SAP Business Suite on non-SAP HANA databases.

Answer 320

There is no requirement to copy data from SAP Business Suite to SAP HANA.

Answer 321

It offers a simplified landscape where SAP Business Suite and SAP HANA Live share the same in-memory tables.

Answer 322

SAP HANA CDS

Answer 323

More use cases are available with calculation views than CDS

Answer 324

Not all features and settings relevant to BI are available with CDS.

Answer 325

More optimization possibilities are available with calculation views

Answer 326

Calculation views can define the persistence layer as well as data modeling layer

Answer 327

To identify the longest running SQL statements.

Answer 328

To investigate the generated SQL for each node in my calculation view.

Answer 329

To highlight syntax errors in my SQL code.

Answer 330

Join nodes.

Answer 331

Union nodes.

Answer 332

Projection nodes.

Answer 333

Data lineage

Answer 334

Column lineage

Answer 335

Impact analysis

Answer 336

Persistence layer

Answer 337

User interface

Answer 338

Business logic

Answer 339

Data modeling

Answer 340

The project is not assigned to a Space.

Answer 341

Building a project does not generate the database objects defined in its HDB modules.

Answer 342

You do not have the Developer role in the assigned Space.

Answer 343

Calculation view

Answer 344

Logical schema

Answer 345

User-provided service

Answer 346

Development

Answer 347

A reusable analytic privilege that can be used for several users who need to access different data.

Answer 348

An analytic privilege that takes its filter values from variables defined in the calculation view

Answer 349

A temporary analytic privilege that has a defined time validity set for its use

Answer 350

Obscuring column values by hiding some or all characters with replacement characters

Answer 351

Replacing column values with a higher level group such as replacing a person id with team name

Answer 352

Removing complete rows of data that should not be seen by users

Answer 353

To hide sensitive data using alternative characters such as ‘XXXXX’.

Answer 354

To hide sensitive data by adding noise at the record level so that aggregated values still make sense but individual records are not exposed.

Answer 355

To remove complete records so that they cannot be seen by unauthorized users

	Criado por ERNESTO L MARQUEZ F aproximadamente 5 anos atrás

Próximo

E_HANAAW_14 ABAP for SAP HANA

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Questão 29

Questão 30

Questão 31

Questão 32

Questão 33

Questão 34

Questão 35

Questão 36

Questão 37

Questão 38

Questão 39

Questão 40

Questão 41

Questão 42

Questão 43

Questão 44

Questão 45

Questão 46

Questão 47

Questão 48

Questão 49

Questão 50

Questão 51

Questão 52

Questão 53

Questão 54

Questão 55

Questão 56

Questão 57

Questão 58

Questão 59

Questão 60

Questão 61

Questão 62

Questão 63

Questão 64

Questão 65

Questão 66

Questão 67

Questão 68

Questão 69

Questão 70

Questão 71

Questão 72

Questão 73

Questão 74

Questão 75

Questão 76