Test your basic knowledge |

Database Management

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. The DML statement used to choose data from a database. The result is stored in a temporary table - called the result-set.






2. A query that removes records which match the criteria you specify from one or more tables






3. No multiple multi-valued dependencies.






4. Relations which allow you to retrieve related records from the same table.






5. A query that copies data or changes data in some way. This includes append - delete - make-table and update queries.






6. The part of an SQL statement that specifies which record to retrieve.






7. A database object that prints information formatted and organised according to your specifications.






8. A graphical representation of any portion of a database scheme.






9. The actual pieces of facts that are stored in the fields in a database table.






10. A collection of fields that together describe one entity.






11. The conditional expession that is to be used to select particular data records from a larger set of records.






12. Candidate key selected for use.






13. A normalization which falls between 3NF and 4NF and involves the elimination of non-trivial dependencies






14. That structure which contains description of objects created by a user - such as base tables - views and constraints - as a part of a database.






15. An association between two tables in which several records in one table can relate to 0 - 1 or many records in the other table.






16. The components of a data abase i.e. tables - queries - forms - reports - pages - macros and modules.






17. A data type that is used for fields and calculations involving money






18. An association/link established between common fields in two different tables. A relationship can be one-to-one - many-to-many or more usually one-to-many.






19. A data model in which the data is organized into a tree-like structure. The structure allows representing information using parent/child relationships: each parent can have many children - but each child has only one parent






20. A record as seen in the data sheet view.






21. A database computer language designed for the retrieval and management of data in relational database management systems (RDBMS) - database schema creation and modification - and database object access control management.






22. An association between two tables in which the primary key value of each record in the primary table corresponds to the value in the matching field or fields of one and only one record in the related table.






23. Data from a table - form - query which is displayed in a row-and-column format.






24. A primary key that is comprised of more than one field.






25. A central repository for databases across an entire enterprise.






26. A question about the data stored in your tables - or a request to perform an action on the data. A query can bring together data from multiple tables to serve as the source of data for a form. report or data access page.






27. Many-to-many relationships occur when each record in TableA may have 0 - 1 or many linked records in TableB and vice-versa.






28. The program which is used to organize - access and manage the data in a database - Creates - processes - and administers databases.






29. This is an exact numeric data type that holds from 10^38 - 1 through 10^38 - 1.






30. A relational database management system from Microsoft that combines the relational MS Jet Database Engine with a graphical user interface and software-development tools.






31. Functional dependency involving only non-key attributes.






32. The persons or things that a database table is about.






33. Specialized engines designed specifically to store objects. Users can interact with objects only through designated methods.






34. The process of organizing data to minimize redundancy and produce smaller - well-structured relations/tables.






35. A database object on which you place controls for entering - displaying and editing records in a table.






36. A field in a table with unique values that although it is not the primary key - it could have been used as such.






37. A feature that speeds up searching and sorting in a table based on key values and can enforce uniqueness on the rows of a table.






38. DOC MADE UP






39. A table which is not only in 2NF but whose non-primary key fields are dependent only on the primary key and therefore have no dependence on (relationship to) any other non-primary key field in the table.






40. A self-describing collection of integrated tables. The tables are called integrated because they store data about the relationships between the rows of data.






41. Knowingly violates one or more rules of normalization.






42. A Key composed of more than one attribute.






43. An attribute utilized to sort and/or identify data in some manner. Each table should have a primary key which uniquely identifies records.






44. A control - also called an edit field - used on a form - report or data access page to display text or accept data entry.It can have a label attached to it.






45. The set of fields in a table which stores unique values and so any one from the list can be selected to be the primary key.






46. A way of looking at a database object - usually looking at the design or at the contents/results






47. The process of examining and analyzing data with a view to extracting patterns from it. It is usually done on data warehouses






48. A characteristic of the items in a database i.e. a field






49. This is a property of data which - when satisfied - requires every value of one field (attribute) of a table to exist as a value of another field in another related table.






50. A candidate key that coud have been the primary key but was not selected as such ; OR a field that is not the primary key but has been used for indexing nevertheless.