BW330 - SAP BW Modeling & Implementation Flashcards
~Modeling with SAP HANA, you can use a virtual table in a view. Which of the following are advantages of this virtual data model?~
- The result set is stored as SAP HANA row store rable.
- You can use data from external sources.
- The data footprint is reduced.
- Data is only replicated once.
- The data is always up-to-date.
-The result set is stored as SAP HANA row store rable.
(+)-You can use data from external sources.
(+)-The data footprint ie reduced.
-Data is only replicated once.
(+)-The data is always up-to-date.
~Using a virtual data model, the model is easily changed by changing the remote table, the data footprint is non-existent because no data is loaded and the data is always up-to-date because the queries are executed on real-time data. Data is never replicated for a virtual model because the data remains in the source table and is read from there, not from a SAP HANA table. Read more in the lesson, Understanding SAP HANA from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~SAP HANA provides a choice of row or column storage types~
- True
- False
(+)True
-False
~SAP HANA provides a choice of either row or column storage types. Read more in the lesson, Understanding SAP HANA from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~Which of the following are Best Practice options for storing data in a BW system running on SAP HANA?~
- Store the bulk of the data on disk for retrieval when required (warm data)
- Store the most relevant data in a compressed column store (hot data)
- Split the most relevant data by date and store between an uncompressed column store and tables stored on disk (warm data)
- Store all data in compressed column stores to maximize performance (hot data)
- Move less important data into an external storage system (cool data)
(+)Store the bulk of the data on disk for retrieval when required (warm data)
(+)Store the most relevant data in a compressed column store (hot data)
-Split the most relevant data by date and store between an uncompressed column store and tables stored on disk (warm data)
-Store all data in compressed column stores to maximize performance (hot data)
(+)-Move less important data into an external storage system (cool data)
~There are three alternatives for storing data using SAP HANA - store the most relevant in memory as ‘hot’ data; store mass data on disk in BW as ‘warm’ data; and leave less important data in an external system as ‘cool’ data. There is no option in SAP HANA to split data by date to create warm data. Storing all data in memory is technically possible but it would not be a Best Practice because of the cost of doing so. Read more in the lesson, Understanding SAP HANA from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~Which of the following are golden rules for modelers using SAP HANA?~
- Save less important data outside of memory
- Use column store for analytical tasks
- Virtual data sources should use SAP HANA as the physical database
- Be economical and re-use SAP HANA Views when possible
- Avoid calculations within SAP HANA
(+)Save less important data outside of memory
(+)Use column store for analytical tasks
-Virtual data sources should use SAP HANA as the physical database
(+)-Be economical and re-use SAP HANA Views when possible
-Avoid calculations within SAP HANA
~The best practices for a data modeler in SAP HANA are to save less important data outside of memory, use column stores, reuse SAP HANA Views, and modularize and parallelize. A virtual data source does not have to reside on an SAP HANA database. Read more in the lesson, Understanding SAP HANA from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~The SAP BW architecture is made up of the extraction layer, the data layer, and the reporting layer.~
- True
- False
(+)-True
-False
~The SAP BW architecture is made up of the extraction, data, and the reporting layers. Read more in the lesson, Understanding SAP HANA from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~Based on BW 7.5, which of the following should be considered when modeling master data and transaction data?~
- If master data does not need to replicated, an Open ODS View for texts and attributes could be used
- If transaction data should be stored , an Advanced Data Store Object (ADSO) should be used
- To load transaction data efficiently, an Open ODS View of type facts should be used
- Without additional data load, combine data from existing InfoProviders using a CompositeProvider
- If master data is to be persisted, then chracteristics should be used
(+)If master data does not need to replicated, an Open ODS View for texts and attributes could be used
(+)If transaction data should be stored , an Advanced Data Store Object (ADSO) should be used
-To load transaction data efficiently, an Open ODS View of type facts should be used
(+)Without additional data load, combine data from existing InfoProviders using a CompositeProvider
(+)If master data is to be persisted, then chracteristics should be used
~All of the listed options are appropriate for BW 7.5, except for loading using an Open ODS View. Open ODS Views are not used to load data, they are only used to view data during query execution. Read more in the lesson, Understanding SAP HANA from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~Storing raw data in PSA data packages is recommended when the data will update multiple data targets or when the amount of data being extracted is large.~
- True
- False
(+)True
-False
~Storing data in PSA is always recommended when the PSA data updates several diiferent targets PSA is also used to store data when the extraction volumes are high, because this alleviates using resources in the remote system while the entire load takes place. Read more in the lesson, Understanding SAP HANA from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~You want to implement a complex data quality improvement scenario that requires a stable set of reference data. Which model focus would you choose?~
- The source system
- SAP HANA
- SAP BW
-The source system
-SAP HANA
(+)SAP BW
~If you want to improve the data quality in different steps, especially when you need a stable set of reference data. SAP BW is a good choice because it provides features to take snapshots regularly, enrich and keep the data for a long time. In the source system, data is rarely kept online for years. SAP HANA is mainly used for real-time access. Read more in the lesson, Compairing SAP BW with SAP HANA, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Understanding SAP HANA from a Modeling Perspective.~
~If the data source supports it and if the extraction is fast enough, the ODP based dataflow without PSA is recommended because it helps to reduce the volume of redundantly stored data.~
- True
- False
(+)True
-False
~If the data source supports it and if the extraction is fast enough, the ODP based dataflow without PSA is recommended because it helps to reduce the volume of redundantly stored data. Data in the delta queue is compressed and can be used for different targets. Read more in the lesson, Understanding SAP BW from a Modeling Perspective, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Compairing SAP BW with SAP HANA.~
~If a new field is added to key definition of a database table, less records can be distinguished.~
- True
- False
-True
(+)False
~If more fields are part of the key definition of a database table, more criteria exist to distinguish records, and rather more different records can be distinguished.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Business Review. Lesson: Understanding the ERP Model.~
~One purpose of investigating the source models of different source systems is to check which homogenization of master data is necessary.~
- True
- False
(+)True
-False
~Homogenizing master data and preparing transactional data from different sources are typical tasks of BW projects. In order to judge the required steps, investigating the source models is required. Read more in the Lesson Understanding the ERP Model in BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Business Review. Lesson: Understanding the ERP Model.~
~In a productive landscape, SAP Best Practice is to have at least a development system, a quality assurance system and a productive system.~
- True
- False
(+)True
-False
~SAP always recommends that there are at least three technical systems - development, QA, and production. Read more in the lesson, Planning Transport Management, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Global Decision Areas and Best Practice Standards. Lesson: Planning Transport Management.~
~The productive BW system is always defined as a closed system in which changes can only be made by importing a transport.~
- True
- False
-True
(+)False
~BW systems are normally an open system because alterations to objects like queries and query views should be possible. Changes to these objects are not seen as harmful. Read more in the lesson, Planning Transport Management, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Global Decision Areas and Best Practice Standards. Lesson: Planning Transport Management.~
~Which of the following are advantages of separating master data and transactional data?~
- Referential integrity of transaction data can be assured because records without matching master data will not be loaded
- Time-dependent data can be modeled simply
- Harmonization of master data with multiple source systems can be achieved with system-specific master data tables
- Texts can be stored in multiple languages
- Storage costs are reduced because data is only stored once
-Referential integrity of transaction data can be assured because records without matching master data will not be loaded
(+)Time-dependent data can be modeled simply
-Harmonization of master data with multiple source systems can be achieved with system-specific master data tables
(+)Texts can be stored in multiple languages
(+)Storage costs are reduced because data is only stored once
~All the items listed are advantages of separate master data except for the harmonization response. Harmonization of data from different systems is possible using single master data tables with the inclusion of the source system ID as characteristic in the table. Read more in the lesson, Separating Master Data and Transactional Data, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Global Decision Areas and Best Practice Standards. Lesson: Separating Master Data and Transactional Data.~
~To model the tracking history scenarios of historical truth and current truth, two different star schemas are required.~
- True
- False
-True
(+)False
~The modeling of current and historical truth can be modeled in a single star schema using a mixture of time-dependent and time independent navigation attributes. Read more in the lesson, Implementing Tracking History Scenarios, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Global Decision Areas and Best Practice Standards. Lesson: Tracking History.~
~Which of the following statements are true regarding the difference between commanding end concatenation?~
- Compounding is easier to filter in queries because the objects are separate whereas with concatenation, the key string needs to be masked
- Compounding is easier for users to understand because it is based on a 1:1 object mapping but concatenation is more complex for users to understand and decipher
- Concatenetion uses a single key value but compounding uses more then one
- Adding key fields in concatenation is easier because only the transformation needs to be changed but in compounding structures need to be changed and data re-loaded
- Concatenation is supported in the definition of the InfoObject whereas compounding is only relevant for transactional data
(+)-Compounding is easier to filter in queries because the objects are separate whereas with concatenation, the key string needs to be masked
(+)-Compounding is easier for users to understand because it is based on a 1:1 object mapping but concatenation is more complex for users to understand and decipher
(+)-Concatenetion uses a single key value but compounding uses more then one
(+)-Adding key fields in concatenation is easier because only the transformation needs to be changed but in compounding structures need to be changed and data re-loaded
-Concatenation is supported in the definition of the InfoObject whereas compounding is only relevant for transactional data
~All of the responses are true regarding the differences except for the question regarding the
definition of InfoObjects. Compounding. not concatenation is supported in the definition of an InfoObject. Both methods are relevant for master and transactional data. and separate database tables are always created for lnfoObiects whether or not they are compounded or concatenated. Read more in the lesson, Designing a Layered Scalable Architecture (LSA) With Virtual Layers, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Global Decision Areas and Best Practice Standards. Lesson: Designing a Layered Scalable Architecture (LSA) With Virtual Layers.~
~SAP recommends to define queries only on top of a virtual data mart layer. This virtual data mart layer should contain Composite Providers in which fields and lnfoObiects from one or more lnfoProviders can be combined and enhanced with navigational attributes.~
- True
- False
(+)True
-False
~SAP recommends to define queries only on top of a virtual data mart layer with Composite
Providers in which fields and InfoObiects from one or more InfoProviders can be combined and enhanced with navigational attributes. Moreover, this layer enhances your flexibility. You can hide model changes in the underlying InfoProviders from business users. Read more in the lesson, Designing a Layered Scalable Architecture (LSA) With Virtual Layers, in the course BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Data Warehouse Modeling. Unit: Data modeling with SAP Business Information Warehouse (SAP BW) Powered by SAP HANA. Lesson: Designing a Layered Scalable Architecture (LSA) With Virtual Layers.~
~Which of the following are ways in which joins can be made using SAP BW on SAP HANA?~
- A BW InfoSet can be used to create a temporal join
- A native SAP HANA calculation view can perform inner and outer joins
- An Advanced DSO can create joins between master data and transaction data
- BW Composite Provider can provide inner and outer joins
- Transformations can perform joins of multiple DataSources
(+)-A BW InfoSet can be used to create a temporal join
(+)-A native SAP HANA calculation view can perform inner and outer joins
-An Advanced DSO can create joins between master data and transaction data
(+)-BW Composite Provider can provide inner and outer joins
-Transformations can perform joins of multiple DataSources
~Joins can be created using InfoSets, calculation views, and Composite Providers. ADSOs do no have the capability to join master data and transaction data; they store the master data keys in the transaction data record. Transformations are a tool for modifying data as it is moved around BW and they cannot join data.
Read more in the lesson, Understanding LSA++Domains, in the course, BW330H.
Read more in course BW330H SAP BW powered by SAP HANA: Global Decision Areas and Best Practice Standards. Lesson: Understanding LSA++Domains.~