Data Harmonization — Learn free

Self-check

Questions 1–10 of 10

1. How does Data Harmonisation go one step beyond Data Integration, Data Blending, Data Warehousing and Data Marts?
Question 1A. It only connects to a single source systemB. It standardises data from multiple source systems into one unified format, becoming a bridge between data and business requirementsC. It stores data without any transformationD. It removes the need for business stakeholdersE. It replaces ETL with manual data entry
2. What does 'one unified format' mean in the context of Data Harmonisation?
Question 2A. All data is stored as textB. All data is stored in a single tableC. All data is converted to a single currencyD. Data is converted in such a way that it becomes accurate for someoneE. All data is stored in a spreadsheet
3. Harmonising data in one location for a specific department can be called what?
Question 3A. A Data MartB. A Data LakeC. A Data MashupD. A Data SwampE. A Data Mesh
4. Defining standard naming conventions, data types and codes from multiple sources in one unique format is described as harmonising data for what?
Question 4A. Data LineageB. Data VisualisationC. Master Data ManagementD. Data MonetisationE. Data Splitting
5. Gathering metadata details of all source systems, data lakes, warehouses and marts up to reports and dashboards is harmonising data for what?
Question 5A. Data MartsB. Master Data ManagementC. Data EnrichmentD. Data EthicsE. Data Lineage
6. Why is the involvement of business stakeholders described as a must-have step in Data Harmonisation?
Question 6A. Because they approve the IT budgetB. Because they write the ETL codeC. Because without functional knowledge, garbage will flow inD. Because they own the database licencesE. Because they define the latitude and longitude values
7. Which of the following is NOT one of the ideal steps for conducting Data Harmonisation?
Question 7A. Understand the vision of the business requirements, that is, what the converted data will be used forB. Set the baseline by identifying all relevant source systems, tables and columnsC. Define standard processes and actions such as ETL, ELT or manual stepsD. Skip reconciliation once the initial load is completeE. Define metadata at each step of the harmonisation process
8. Which department is used as the example of one that can perform poorly without harmonised data, and what does it depend on?
Question 8A. The Marketing department, which depends on product names, codes, sales locations, timing and buyer details to plan campaignsB. The Legal department, which depends on contract templatesC. The HR department, which depends on leave balancesD. The IT department, which depends on server logsE. The Facilities department, which depends on printer ink orders
9. Would the details harmonised for the Marketing department be equally relevant to the Finance department?
Question 9A. Yes, every department needs exactly the same harmonised detailsB. No, for the Finance department the harmonisation steps and required details will be totally differentC. Yes, because Finance owns the marketing budgetD. No, because Finance does not use dataE. Yes, because harmonisation always produces one universal dataset
10. What is the first ideal step in conducting Data Harmonisation?
Question 10A. Define the ETL processesB. Reconcile the loaded dataC. Define metadata for every tableD. Buy a Master Data Management toolE. Understand the vision of the business requirements, that is, what purpose the converted data will serve