In a database management system, a query language is primarily designed to do which of the following?

Introduction / Context:
Database management systems separate different kinds of languages for different tasks, such as defining structures, manipulating data, and controlling access. A query language is a special category that focuses on retrieving and sometimes modifying data in a way that is friendly for end users and analysts. This question checks whether you can distinguish the role of a query language from other parts of a DBMS such as data definition or administration tools.

Given Data / Assumptions:

• We are talking about a DBMS that supports a high level query language like SQL.
• End users may not be professional programmers but need to access data.
• The question asks about the primary design goal of the DBMS query language.

Concept / Approach:
A query language such as SQL is designed to express data retrieval and manipulation requests in a declarative, user friendly way. Users specify what data they want rather than how to retrieve it step by step. Query languages often use syntax that resembles English phrases, for example SELECT, FROM, WHERE, and ORDER BY, which makes them easier for non programmers to learn compared to imperative programming languages. While SQL also includes features for data definition, the core idea of a query language is to provide a powerful yet understandable way to ask questions about the data.

Step-by-Step Solution:
Step 1: Review option A, which focuses only on specifying the structure of the database. That is mainly the role of a data definition language, not the full purpose of a query language. Step 2: Review option B, which mentions supporting programmers in developing complex application software. While SQL can be embedded in applications, full application development relies on programming languages, not on the query language alone. Step 3: Review option C, which states that a DBMS query language supports end users by allowing English like commands to retrieve and manipulate data. This matches the main design goal of a high level query language. Step 4: Review option D, which attributes automatic backup, recovery, and user management to the query language. Those are administrative functions, typically handled by DBMS tools and system commands, not by the query language itself. Step 5: Conclude that option C correctly describes the purpose of a DBMS query language.

Verification / Alternative check:
Looking at SQL, most of the time users write SELECT, INSERT, UPDATE, and DELETE statements to work with data in tables. These statements use readable, structured syntax that is easier for analysts and business users to learn than a full programming language. System tasks such as backup or recovery are usually done through separate utilities or DBA commands, confirming that the query language is primarily for data queries and simple data updates.

Why Other Options Are Wrong:
Option A is incorrect because defining the structure of a database is specifically the job of the data definition language, which is a subset of SQL but not the entire idea of a query language. Option B is incorrect because complex application development requires control structures, user interfaces, and other features that go beyond the capabilities of a query language. Option D is incorrect because backup, recovery, and user management are administrative features that are not part of the query language design goal.

Common Pitfalls:
Learners sometimes confuse the categories of database languages and think that SQL is purely for structure or administration, when in practice it covers several sublanguages. Another pitfall is assuming that a query language must be procedural, while in reality languages like SQL are declarative. It is also common to underestimate how accessible query languages are to non technical users, even though many business users successfully learn SQL for reporting tasks.

Final Answer:
A DBMS query language is primarily designed to support end users by allowing English like commands to retrieve and manipulate data from the database.