nerdexam
Novell

050-696 · Question #16

Your company's business procedures require the use of triplicate forms. To accommodate this, you have purchased a dot-matrix printer to deploy in your network. The printer will be connected directly…

The correct answer is A. Yes, all prerequisite requirements have been met. iPrint supports printers without embedded Printer Agents by allowing a software Printer Agent to be created on the Print Manager, and parallel cable connections to an LPT port are a valid supported attachment method.

Server Management and Maintenance

Question

Your company's business procedures require the use of triplicate forms. To accommodate this, you have purchased a dot-matrix printer to deploy in your network. The printer will be connected directly to one of your server's LPT ports using an IEEE 1284 parallel cable. You use iPrint to provide print services to your end users. This printer doesn't have an embedded printer agent. Can it be used with iPrint?

Options

  • AYes, all prerequisite requirements have been met.
  • BNo, the Print Manager doesn't support dot-matrix printers.
  • CNo, the iPrint Broker is incompatible with IEEE 1284 printers.
  • DNo, iPrint doesn't support printers without an embedded printer agent.
  • ENo, a Printer Agent can't be created for printers that use a parallel cable.

How the community answered

(60 responses)
  • A
    75% (45)
  • B
    3% (2)
  • C
    7% (4)
  • D
    2% (1)
  • E
    13% (8)

Why each option

iPrint supports printers without embedded Printer Agents by allowing a software Printer Agent to be created on the Print Manager, and parallel cable connections to an LPT port are a valid supported attachment method.

AYes, all prerequisite requirements have been met.Correct

An embedded Printer Agent is not a requirement for iPrint; an administrator can create a Printer Agent on the Print Manager to represent any locally attached printer, including one connected via an IEEE 1284 parallel cable to a server LPT port. Dot-matrix printers are not excluded by iPrint, so the scenario as described fulfills all requirements for a functional iPrint deployment.

BNo, the Print Manager doesn't support dot-matrix printers.

The Print Manager applies no restrictions based on printer technology type such as dot-matrix impact printing; it supports any printer for which a Printer Agent can be created.

CNo, the iPrint Broker is incompatible with IEEE 1284 printers.

The Broker manages driver storage and event notifications and does not evaluate or restrict printers based on their physical interface cable type.

DNo, iPrint doesn't support printers without an embedded printer agent.

iPrint does not require an embedded Printer Agent; a Printer Agent hosted on the Print Manager can represent printers connected to a server port, making this answer factually incorrect.

ENo, a Printer Agent can't be created for printers that use a parallel cable.

The physical connection type, including an IEEE 1284 parallel cable attached to an LPT port, does not prevent Printer Agent creation on the Print Manager; such locally attached printers are explicitly supported.

Concept tested: iPrint Printer Agent creation for locally attached printers

Source: https://www.microfocus.com/documentation/open-enterprise-server/2023/iprint-linux-administration-guide/

Topics

#iPrint#printer compatibility#parallel cable#printer agent

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 050-696 Practice