You have an existing field-based data flow that follows the LSA++ concept. To meet a new urgent business requirement for a field you want to leverage a hierarchy of an existing characteristic without changing the transformation. How can you achieve this? Note: There are 2 correct answers to this question.
Answer : B
Which data deletion options are offered for a standard DataStore object (advanced)? Note: There are 3 correct answers to this question.
Answer : A, B, C
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?
Answer : B
"You created an Open ODS View on an SAP HANA database table to virtually consume the data in SAP BW/4HAN
Answer : A, A, C, D
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.
Answer : B, C
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.
Answer : A, C
* 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/
"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?
Answer : C
* 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