Database Management Systems Quiz

A structured collection of related data.

A database's purpose is to store data, provide structure for it, and allow users to interact with it through methods like querying, adding, updating, and deleting information.

Database properties describe the real world aspect it represents, the inherent meaning of its data, its data model type, and its purpose for specific users and applications.

A database is considered traditional if it mainly stores textual or numerical related data and supports relationships between them. Examples include MySQL, Oracle, and PostgreSQL.

A database is considered non-traditional when it handles data beyond text or numbers, like images, tweets, or videos. It might not emphasize relationships as much. Examples include NoSQL databases, Graph databases, and cloud storage for big data.

Data abstraction simplifies the complexity of data storage and organization by hiding irrelevant details, allowing users to interact with data at their preferred level. It promotes data independence.

Conceptual modeling is the initial phase of database design, focusing on high-level general design using models like Entity-Relationship (ER).

Logical modeling in database design involves translating the conceptual model into a specific database model, such as the relational model.

The ability to change the database schema at one level of abstraction without affecting the next higher level.

The ability to change the database schema at the conceptual level without affecting applications.

The ability to change the physical level of the database (e.g., storage method) without affecting the conceptual level or applications.

Software specifically designed to create, maintain, and manage a database.

The combination of hardware and software used by the DBMS to store and manage data.

Software that interacts with the database and provides a user interface for end-users.

Individuals who manage the database, its content, and related software. They ensure secure access, monitor performance, and acquire resources.

Individuals who design the database schema based on user requirements, including data abstraction, modeling, and identifying entities and relationships.

A database architecture where all components, including client software, server, and database, reside on the same computer.

An architecture where the client interacts with a dedicated server that manages the database, allowing for centralized data control and management.

An architectural pattern dividing the database system into three tiers: presentation (client), application logic, and data (database).

The user interface software provided by the DBMS, typically used to interact with the database.

The computer or machine that runs the database management system and stores the data.

Application programming interfaces (APIs) allow client software to communicate with and manipulate the database.

The user interface and business logic of the application are implemented on the client side in a 2-tier architecture.

Connection to the database and processing of database queries are handled by the server in a 2-tier architecture.

A software program installed on a user's device, allowing them to interact with a web server. Examples include web browsers, mobile apps, and desktop applications.

A three-layered architecture with distinct roles: the client (user's device), the server (processing data), and the database (storing data). This design is common in web applications.

The user's interface, allowing them to interact with the web application. Includes the visual elements, design, and how data is displayed.

The logic and actions that process data in the background. Also known as server-side programming, this tier handles calculations, data manipulation, and business rules.

A system that stores and manages data. This tier can be accessed via APIs for retrieving and updating information.

A set of rules and procedures for communicating between the client and server tiers, enabling data exchange and function calls.

A type of database where data is stored and managed on a central server. All users access the same data through this centralized authority.

A database system distributed across multiple physical locations, offering improved performance, scalability, and fault tolerance. Data is replicated across multiple servers.

A database system where data is stored and managed on one central server, accessible to all users.

A system with multiple servers storing the same database, replicating and distributing data across different locations for increased availability and performance.

The process of presenting different views of the data structure, simplifying data representation and hiding complexity from users.

The initial phase of database design that uses high-level concepts to describe the database requirements in text or diagrams, communicating with non-technical stakeholders.

Defines the detailed physical storage structure of the database. It includes information about data representation, indexing techniques, and file organization, specifying how data is physically stored.

Specifies the database's logical structure, translating the conceptual model into a specific data model like the relational model.