Data
Raw facts, observations or symbols that have not yet been interpreted in a useful context.
101, Anu, 82, 76, 91
CodeBhavya
Understand why database systems exist, what they manage and how they solve the problems created by separate files and duplicated data.
These terms are related, but they are not interchangeable.
Raw facts, observations or symbols that have not yet been interpreted in a useful context.
101, Anu, 82, 76, 91Data that has been organized, processed or interpreted so it answers a question or supports a decision.
Select a question. The same stored rows can produce different useful information.
| ID | Student | DBMS | C | Mathematics | Average |
|---|
Choose a question to process these rows into information.
Students register, faculty enter marks, and reports request summaries.
Interprets queries, checks rules, coordinates users, protects data and handles recovery.
Tables, relationships, constraints, indexes and metadata form an organized collection.
Files, pages, logs and backups live on disks or managed cloud storage.
| Term | What it means | Example |
|---|---|---|
| Database | The organized collection of related data and its structure. | A college database containing student, course and enrolment tables. |
| DBMS | The software used to define, store, query, secure and recover databases. | PostgreSQL, MySQL, Oracle Database, SQL Server or SQLite. |
| Database system | The complete environment: database, DBMS, applications, users, procedures and hardware. | The entire college registration solution. |
A file is not “bad.” The problem appears when many applications maintain overlapping facts without shared rules.
The same fact is stored repeatedly, consuming space and increasing maintenance.
Copies disagree because one file was changed while another remained old.
Data in different formats and locations is hard to combine reliably.
Rules such as “marks must be 0–100” are duplicated or omitted.
Simultaneous edits can overwrite or expose incomplete changes.
Fine-grained permissions, audit trails and safe crash recovery are difficult.
Change the phone number in only one departmental file and observe the contradiction.
Phone: 98765 10001
Phone: 98765 10001
Phone: 98765 10001
All three copies currently agree, but there is no central rule keeping them synchronized.
Servers, storage, client machines and network devices.
DBMS, operating system, applications and supporting tools.
Operational records plus metadata describing their structure.
Rules for use, backup, recovery, security and maintenance.
Designers, administrators, developers and end users.
Select a role to see its main decisions and responsibilities.
Different domains store different facts, but they need the same core guarantees.
Accounts, transfers and balances demand correctness and recovery.
Patients, visits and prescriptions require privacy and reliable history.
Products, inventory, orders and payments change concurrently.
Students, courses, enrolments, attendance and results are strongly related.
No. A small configuration file or temporary single-user dataset may not need database overhead. Choose a DBMS when data is shared, persistent, related, valuable, frequently queried or governed by important rules.
These are learning checks, not a timed assessment. Each answer explains the reasoning immediately.
Complete the concept checks and mark this level when you can explain the ideas without reading.
Saved in this browser only.