Data transmission scenario: A firm needs to send information from 1,000 punched cards to a remote computer. Which type of terminal would typically be used for this bulk, non-interactive transfer of data?

Introduction / Context:
Punched cards represent historical batch data entry. When an organization wants to transmit a large stack of cards (for example, 1,000 cards) to a host, the workflow is non-interactive and scheduled. This question tests understanding of terminal types and when batch versus interactive methods are appropriate in data communications.

Given Data / Assumptions:

• A stack of 1,000 punched cards must be transmitted.
• The destination is a remote computer, not a local processor.
• The process emphasizes volume transfer over real-time interaction.
• Legacy data-entry and telecom concepts apply (terminals, host links).

Concept / Approach:

Punched card workflows are classically aligned with batch operations. A batch processing terminal is designed to collect a large dataset offline and then transmit it as a block at predetermined times or on demand. This minimizes line usage and operator interaction during transmission, which fits the punched-card context.

Step-by-Step Solution:

Verification / Alternative check:

Operationally, older data centers used card readers connected to communication front-ends. Data would be staged and then shipped to the host in blocks. This confirms that batch transfer mechanisms, rather than interactive point-of-sale or conversational terminals, were the norm for such workloads.

Why Other Options Are Wrong:

• POS terminal: Optimized for retail transactions, not bulk card stacks.
• Data collection terminal: May capture data, but does not specifically emphasize batch transmission to a remote host.
• Intelligent terminal: Provides local processing, usually interactive; not necessary for card-batch transmission.
• None of the above: Incorrect because batch processing terminal matches precisely.

Common Pitfalls:

Confusing data collection (gathering) with batch transmission (scheduled, bulk send). Also, assuming that any terminal with local logic is optimal; in this use case, the workload pattern is the key determinant.

Final Answer:

batch processing terminal