Test your basic knowledge |

Data Warehousing

Subject : it-skills
Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Issues to consider when deciding EDW architecture: 1. Which database management system (DBMS) should be used? (ex: Crash Data" MS SQL) 2. Will ______________________ be used? 3. Will data migration tools be used to load the data warehouse?4. What too






2. Extract - Transform and Load






3. All database architectural fall into one of these two categories: EDW or _________ (independent data marts - data mart bus architecture - hub and spoke architecture - centralized data warehouse - federated data warehouse)






4. A query created by a BI user






5. Fifth stage of building a data mart






6. Tables containing summary records calculated from the main fact tables






7. A group of conformed dimensions






8. Second stage of building a data mart






9. Unlike independent data marts the marts are linked via middleware






10. A database table that maps (e.g.) manufacturing product IDs to sales product IDs






11. Take data from a source system






12. A tool that allows users to write queries without having to learn SQL






13. A table containing foreign keys and values






14. Used to support day-to-day operations






15. These extend BI into automating and optimising processes






16. Business applications - methods and tools that support the caputre and use of master data






17. The operational systems - data warehouse and data marts






18. simplest and least costly architecture developed to operate independently of each other - poor solution






19. Look-up tables referred to by fact tables






20. The level of detail required for a fact to be useful






21. First stage of the data warehouse data architecture design process






22. A logical design technique that presents data in a way that is optimised for high-performance access






23. A single low-level fact representing a single business operation






24. A summary record for a specific reporting period






25. Second stage of the data warehouse data architecture design process






26. Splitting data tables into smaller tables for efficient access.






27. Data about the data






28. A group of related fact tables






29. A simplified form of a data warehouse supporting the work of a single line of business






30. Import data into a new database






31. A system that allows people to access and analyse data for business management and performance improvement






32. Requesting more information about a particular fact






33. Extract - Load and Transform






34. The business applications






35. Make changes to data so that it is compatible with a new database






36. Third stage of building a data mart






37. First stage of building a data mart






38. Online Analytical Processing






39. A daily snapshot for each day of a set period






40. A report created by an IT department user






41. An operational system that provides data for a business information system






42. Requesting information about related facts






43. Fourth stage of the data warehouse data architecture design process






44. Draws data from operational or external systems






45. A schema where dimensions are only connected to facts






46. Third stage of the data warehouse data architecture design process






47. Fourth stage of building a data mart






48. A computer system used to support the day-to-day operations of an organisation






49. Most famous data warehouse where a maintable infastructure includes a centralized data warehouse that serves for the needs of all organizational units (most favored 39 percent)






50. An alternative term for a data warehouse