Across record-management systems, which primitive operations are universally supported for basic data handling and retrieval tasks?

Introduction / Context:
Whether a system is a legacy file manager or a modern relational DBMS, there are baseline operations that enable users to prepare, find, and present data. Recognizing these core capabilities helps learners map high-level requirements to the correct low-level tools in any environment.

Given Data / Assumptions:

• We consider generic record-management functions, not vendor-specific features.
• Sorting organizes records for reporting or analysis.
• Look-up retrieves records matching criteria.
• Printing or report output renders the data for consumption.

Concept / Approach:

Core primitives generally include sorting (by keys/fields), look-up (exact match or condition-based retrieval), and print/report generation (formatting results). Even sophisticated systems build complex features atop these fundamentals, such as indexed look-ups, ORDER BY sorts, and reporting services for printed or electronic output.

Step-by-Step Solution:

Verification / Alternative check:

From early flat-file managers to SQL engines, ORDER BY (sort), SELECT ... WHERE (look-up), and reporting/printing facilities are ubiquitous, confirming the selection.

Why Other Options Are Wrong:

Choosing only one primitive ignores the broad, minimal toolset needed for practical record handling.

None: Incorrect because the listed operations are standard features.

Common Pitfalls:

Overlooking that printing today includes electronic reports and exports, not just paper hard copies.

Final Answer:

All of the above