Purpose of report generators: In information systems, what are report generators typically used to do?

Introduction / Context:
Report generators and modern BI/reporting tools transform stored data into organized outputs for decision-making. They sit above the database, focusing on querying, grouping, summarizing, and formatting data for end users, analysts, and auditors.

Given Data / Assumptions:

• The tool’s focus is generating reports, not primary data capture.
• Common capabilities include data retrieval and answering user queries through parameterized reports.
• We assume integration with databases or data warehouses.

Concept / Approach:
Report generators are read-oriented. They retrieve information from files/tables and support query-based slicing and dicing. While they may include simple data entry prompts (report parameters), they are not used to store transactional input; that is the role of OLTP applications or ETL processes.

Step-by-Step Solution:
Identify tasks aligned with reporting: retrieval and answering queries.Eliminate data input/storage as a core function of report generators.Select the combined option covering retrieval and queries.

Verification / Alternative check:
Examples (SSRS, Crystal Reports, JasperReports, Power BI paginated) emphasize querying and presentation, not data entry or storage. They connect to data sources, execute queries, and render outputs (PDF, Excel, dashboards).

Why Other Options Are Wrong:

• Store data input by a user: That is an application or form processing function.
• Retrieve only or answer only: Too narrow; robust report tools do both.
• None of the above: Incorrect because report generators clearly retrieve and answer queries.

Common Pitfalls:
Expecting report tools to perform heavy ETL or transactional writes; they are optimized for read, aggregation, and presentation.

Final Answer:
both (b) and (c)