Client–server DBMS definition A _____ DBMS distributes data processing tasks between the user’s workstation (client) and a network server (database server).

Introduction / Context: Client–server architecture splits application responsibilities between client machines and central servers. In database environments, this model allows user interfaces and some business logic to run on the client while heavy data processing and storage are handled by the server, improving scalability and manageability.

Given Data / Assumptions:

• The client communicates with a DBMS on a server over a network.
• Work can be divided: UI and request formatting on the client; concurrency control, query optimization, and storage on the server.
• The term sought describes this distribution model.

Concept / Approach: A client–server DBMS architecture centralizes data management while allowing many clients to connect concurrently. The server enforces integrity and security; clients submit SQL requests and render results. This differs from purely centralized (host-based) or purely local (desktop database) approaches.

Step-by-Step Solution:

Identify the architectural split: client-side presentation/logic vs server-side data services.Map that split to the term “client–server DBMS.”Exclude unrelated classifications (network/hierarchical as logical data models, not deployment architecture).Select “Client Server.”

Verification / Alternative check: Standard systems design references describe client–server as the predominant enterprise model, later extended to n-tier and service-oriented architectures.

Why Other Options Are Wrong: Network/Hierarchical: logical data models from early DBMS history, not architectural roles distribution.

Relational: logical model; can be implemented in client–server or other architectures.

None: incorrect because “Client Server” matches precisely.

Common Pitfalls: Confusing data models (relational, hierarchical) with system architectures (client–server, n-tier).

Final Answer: Client Server