SAP C_BW4H_214 Practice Test - Questions Answers, Page 5

List of questions
Question 41

What are the reasons for implementing CompositeProviders? Note: There are 2 correct answers to this question.
To store snapshots for reporting
To provide an interface for BW queries
To persist combined data for reporting
To provide a virtual data mart layer
Question 42

'You have already loaded data from a non-sap system into SAP Data Wharehouse Cloud. You want to federate this data with data from an InfoCube of your SAP BW powered by SAP HANA system' What do you need to use to combine data?
BW SHEL Migration
BW Remote migration
SAP ABAP Connection
SAP BW/4HANA Model Transfer.
* C. SAP ABAP Connection: This is what you need to use to combine data from a non-sap system and an InfoCube of your SAP BW powered by SAP HANA system using SAP Data Warehouse Cloud. You can use an SAP ABAP connection to connect to your SAP BW system and access the InfoCube data as a remote table. You can then join this remote table with the data from the non-sap system that you have already loaded into SAP Data Warehouse Cloud using a graphical view12.
* 1 https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/release/en-US/0c9d6f0a6c4a4b8e8b3f7e5c0a3d6f9d.html
* 2 https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/release/en-US/5c9a6c8b6c4a4b8e8b3f7e5c0a3d6f9d.html
Question 43

Which disadvantages should you keep in mind when you set the High Cardinality flag for a characteristic? Note: There are 2 correct answers to this question.
You cannot use navigation attributes for this characteristic
You cannot load more than 2 billion master data records for this characteristic
SID numbers are created at runtime which might negatively affetct the reporting performance
You cannot use this characteristic as a navigation attribute for another characteristic.
* A. You cannot use navigation attributes for this characteristic: This is a disadvantage of setting the High Cardinality flag for a characteristic. A characteristic with high cardinality cannot be used as a navigation attribute for another characteristic, and therefore it cannot have navigation attributes itself12.
* C. SID numbers are created at runtime which might negatively affect the reporting performance: This is a disadvantage of setting the High Cardinality flag for a characteristic. A characteristic with high cardinality has no persistent SID values and no SID table, which means that the SID numbers are generated on the fly during query execution. This can have a negative impact on the reporting performance, especially if the characteristic is used in filters or aggregations13.
* 1 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/f851415842154e59a5f038e458b97a0b.html
* 2 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/88a51330c046426091f3730d0c42c0de.html
* 3 https://blogs.sap.com/2019/01/14/high-cardinality-characteristics-in-bw4hana/
Question 44

What are the prerequisites for deleting master data (for example, cost centers) in SAP BW/4HANA? Note: There are 2 correct answers to this question.
There must be no BW analysis authorizations defined thta use any of the cost centers
There must be no transaction data referring to the cost centers
There must be no hierarchy for the cost centers
There must be no BW query that uses cost cenetr as a free characteristics.
Question 45

'You created an Open ODS View on an SAP HANA database table to virtually consume the data in SAP BW/4HANA. Real-time reporting requirements have now changed and you are asked to persist the data in SAP BW/4HANA. Which objects are created when using the ''Generate Data Flow'' function in the Open ODS View editor? Note: There are 3 correct answers to this question.'
Data source
Composite Provider
Transformation
Data Store object (advanced)
SAP HANA calculation view.
Question 46

You have created a custom characteristic with the technical name 'COSTOBJ'. Depending on the controlling area, you need to have different atribute values assigned. How do you desing the model?
Compound characteristic 'COSTOBJ' with the characteristic for Controlling Area
Compound the characteristic for Controlling Area with the characteristic 'COSTOBJ'
Define Controlling Areas as a navigation attribute for the characteristic 'COSTOBJ'
Define characteristic 'COSTOBJ' as a navigation attribute for Controlling Area
Question 47

Which data deletion options are offered for a standard DataStore object (advanced)? Note: There are 3 correct answers to this question.
Deletion of all data from active table only
Request-based data deletion
Selective deletion of data
Deletion of data from all tables
Selection deletion incluiding data of subsequent targets
Question 48

'For InfoObject ADDRESS, the High Cardinality flag has been set. However, ADDRESS has an attribute CITY without the high Cardinality flag.' What is the effect on SID values in this scenario?
SID values are not stored for InfoObject ADDRESS
SID values are generated when data for infoObject ADDRESS is loadet
SID values are generated when InfoObject CITY is activated
SID values are generated when InfoObject ADDRESS is activated.
Question 49

You create a DataStore Object(advanced) using the Data Mart DataStore Object modeling property. Which behaviors are specific to this modelling property? Note: There are 2 correct answers to this question.
The change log table will be filled only after data activation
Reporting is done based on a union of the inbound and active tables
Query result are shown only when data has been activated
The records are treated as if all characteristics are in the key.
* B. Reporting is done based on a union of the inbound and active tables: This is a behavior that is specific to the Data Mart DataStore Object modeling property. The query reads data from both the inbound table and the active table of the DataStore object, which means that it is not necessary to activate the data to be able to see all the data. The data read is consistent and stable, since data is only included up to the first inconsistent request12.
* D. The records are treated as if all characteristics are in the key: This is a behavior that is specific to the Data Mart DataStore Object modeling property. No keys can be specified for this type of DataStore object, but when the data is activated, it is grouped according to the aggregation behavior of all characteristics. Therefore, key figures cannot be overwritten and only additive deltas can be loaded12.
* 1 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/1961a9b62f054cc5a4f0d98485b82fa9.html
* 2 https://help.sap.com/docs/r/dd104a87ab9249968e6279e61378ff66/11.1.0/en-US/9cf20bb96e254f6b9b5bf1c9c1413f35.html
Question 50

What are some of advantages of using SAP BW/4HANA business content? Note: There are 2 correct answers to this question.
Question