Accounting Information Systems (QNO1 / PQNO) Practice Exam

The key idea here is that the database schema is a blueprint that defines how data is organized—what tables or entities exist, the fields they contain, data types, relationships, and constraints. It doesn’t hold the actual data; it describes how data should be stored and related so the system and applications know how to interact with it.

Data independence is the goal of separating how data is viewed and used from how it’s actually stored. There are three levels: external, which defines what individual users or applications see and how they view data; conceptual, which describes the overall logical structure of the entire database (the global organization of data and relationships); and internal, which deals with physical storage details like indexing, file structures, and access paths. Together these levels allow changes in one layer (for example, changing storage formats or adding a new field) without forcing changes in the applications that rely on the data.

So the statement that the database schema defines structure and that the external, conceptual, and internal levels achieve data independence best captures both what the schema does and how data independence across these levels works. It’s not about security policies, it’s not specifically about the data dictionary, and it doesn’t mean the schema stores actual records.