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. Allows multiple CPUs to process multiple queries simultaneously - providing scalability.






2. The business applications






3. A visual display of the most important information needed by a particular user






4. Draws data from a data warehouse






5. Data accessible to the whole data warehouse






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






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






8. 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)






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






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






11. Dimensions which are shared by two or more facts






12. Fourth stage of building a data mart






13. A schema where dimensions may be connected to facts or to other dimensions






14. Third stage of building a data mart






15. Take data from a source system






16. A synonym for Business Intelligence






17. Fifth stage of building a data mart






18. Extract - Load and Transform






19. A group of conformed dimensions






20. Extract - Transform and Load






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






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






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






24. A table containing foreign keys and values






25. Requesting more information about a particular fact






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






27. Requesting information about related facts






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






29. A schema where dimensions are only connected to facts






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






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






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






33. The operational systems - data warehouse and data marts






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






35. A query created by a BI user






36. A report created by an IT department user






37. Data about the data






38. A summary record for a specific reporting period






39. Second stage of building a data mart






40. An alternative term for a data warehouse






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






42. These extend BI into automating and optimising processes






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






44. Look-up tables referred to by fact tables






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






46. 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






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






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






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






50. Used to support day-to-day operations