NEW
Font size
WorksheetsDatabase Fundamentals Quiz
Total questions: 50
Worksheet time: 25mins
What is the primary purpose of a database?
To store raw facts without structure
To enable efficient data management and support decision-making
To replace file systems entirely
To generate metadata automatically
Metadata is best defined as:
Raw facts collected from end-users
The result of processing data to reveal meaning
Data that describes data characteristics and relationships
Information derived from knowledge
Which component acts as an intermediary between users and the database?
Data warehouse
Operating system
Database Management System (DBMS)
Application software
What is a key advantage of using a DBMS?
Increased data inconsistency
Minimized data security
Improved data sharing and integration
Reduced end-user productivity
An enterprise database supports:
A single user at a time
A small group of users
A large number of users concurrently
Only decentralized data storage
In the database system environment, "procedures" refer to:
Physical devices like servers
Rules governing database design and usage
Application programs
Raw facts stored in tables
Which DBMS function enforces user security and data privacy?
Data storage management
Data dictionary management
Security management
Backup and recovery
The data dictionary stores:
End-user data
Index definitions
Metadata (e.g., data characteristics)
Hardware configurations
A Database Administrator (DBA) is responsible for:
Writing application code
Designing user interfaces
Database implementation, maintenance, and security
Only data entry tasks
Distributed databases:
Store all data at a single site
Distribute data across multiple sites
Support only day-to-day operations
Exclude transactional data
The relational model views data:
Physically (how it is stored)
Logically (as tables)
Hierarchically (parent-child relationships)
As network structures
A "relation" in the relational model is implemented as a:
File
Table
Tree
Graph
A composite key is:
A key that can be null
Made up of multiple attributes
Used only for data retrieval
A foreign key in another table
A null value in a database represents:
A zero or blank entry
An unknown, missing, or inapplicable value
A duplicated entry
A default value
Referential integrity ensures that:
Primary keys are unique
Foreign keys match existing primary keys in related tables
All attributes are atomic
No transitive dependencies exist
Controlled redundancy in a relational database:
Increases data anomalies
Is always unnecessary
Enables table linking via shared attributes
Violates normalization rules
A secondary key is used for:
Uniquely identifying table rows
Enforcing referential integrity
Data retrieval purposes only
Linking distributed databases
Which relationship type is ideal in relational database design?
1:1
1:M
M:N
Ternary
The data dictionary provides:
Raw end-user data
A detailed account of table attributes and metadata
Hardware specifications
SQL query results
Functional dependence means:
Attribute A determines Attribute B
Attribute B determines Attribute A
Both attributes are composite keys
Attributes are independent
An ER diagram represents:
Physical storage details
The conceptual database from the end-user perspective
SQL commands
Normalization stages
In ER modeling, an "entity" corresponds to a:
Single row in a table
Table (entity set)
Column attribute
Relationship degree
A multivalued attribute:
Cannot be subdivided
Must be stored physically in the database
Can have multiple values for one entity
Is derived from other attributes
Connectivity describes a relationship's:
Number of participating entities
Classification (e.g., 1:M, M:N)
Minimum/maximum occurrences
Dependence on attributes
Cardinality specifies:
The number of attributes in an entity
The minimum/maximum entity occurrences in a relationship
Whether an attribute is optional
The degree of a relationship
A ternary relationship involves:
One entity
Two entities
Three entities
No entities
Derived attributes:
Must be stored in the database
Can be calculated from other attributes
Are always multivalued
Require composite keys
M:N relationships in ER models:
Are implemented directly in relational databases
Must be resolved into two 1:M relationships
Represent recursive relationships
Require no foreign keys
Business rules are used to determine:
SQL syntax
Connectivity and cardinality
Normalization levels
Hardware requirements
In Crow's Foot notation, attributes are placed:
Inside ovals
In a box below the entity rectangle
On relationship lines
In diamond shapes
SQL is divided into:
Data definition and data manipulation languages
Hardware and software components
Entity and relationship languages
Centralized and distributed commands
The CREATE TABLE command is used to:
Insert data into a table
Define a table's structure
Update existing rows
Delete a table
The NOT NULL constraint:
Ensures attribute uniqueness
Prevents null values in a column
Sets default values
Validates data ranges
Declaring a primary key automatically creates a:
Foreign key
Unique index
Default value
CHECK constraint
To add rows to a table, use:
UPDATE
INSERT
SELECT
COMMIT
The WHERE clause in SELECT queries:
Groups rows
Orders results
Specifies row conditions
Joins tables
To permanently save transaction changes, use:
ROLLBACK
COMMIT
DELETE
UPDATE
DELETE FROM table without a WHERE clause:
Removes all rows from the table
Deletes the table structure
Fails with an error
Removes only duplicate rows
A subquery is:
A standalone query
An outer query
A query embedded within another query
Used only with COMMIT
Dropping a table fails if it is:
The "one" side of a relationship
Empty
A temporary table
In 3NF
Normalization aims to:
Increase redundancy
Minimize data anomalies and redundancies
Denormalize tables
Expand database size
Most business databases are normalized to:
1NF
2NF
3NF
4NF
A repeating group violates:
1NF
2NF
3NF
Referential integrity
A dependency diagram helps identify:
SQL syntax errors
Partial/transitive dependencies
ER relationship degrees
Hardware failures
A table is in 2NF if it is in 1NF and has no:
Transitive dependencies
Partial dependencies
Foreign keys
Null values
Conversion to 3NF removes:
Repeating groups
Partial dependencies
Transitive dependencies
Composite keys
Denormalization is performed to:
Achieve higher normal forms
Improve query performance (despite added redundancy)
Eliminate all data anomalies
Reduce metadata
A defect of unnormalized tables is:
Efficient data updates
Simple indexing
Data redundancy causing inefficiency
No backup requirements
Atomicity in attributes means they are:
Multivalued
Derived
Irreducible (cannot be subdivided)
Optional
During normalization, reconciling conflicting goals involves:
Ignoring business rules
Balancing cost, performance, and structural efficiency
Avoiding ER diagrams
Using only 1NF
