A teaching lab is built from diskless X terminals. Each terminal runs only an X server and asks a central Linux host for a graphical login screen, and the applications then run on that central host. Which protocol carries that request, and what is the main objection to using it beyond the lab's own switch?

LPIC-1 Exam 102-500, objective 106. User interfaces and desktops medium

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

The options

Correct XDMCP, and the objection is that the protocol is unencrypted, so credentials and screen contents cross the network in the clear.

Correct. XDMCP lets an X server query a display manager for a session; the display manager answers by connecting back and drawing the greeter. Neither XDMCP itself nor the X traffic that follows is encrypted, so it belongs on a trusted segment only.

Not correct VNC, and the objection is that each terminal would need its own dedicated framebuffer on the server.

Wrong. VNC exports an existing desktop or a virtual framebuffer to a viewer; it is not how an X server obtains a login greeter. The description given is the classic XDMCP arrangement.

Not correct RDP, and the objection is that it requires a Windows licence per connected seat.

Wrong. RDP is Microsoft's protocol, served on Linux only by add-on software such as xrdp. It plays no part in an X server requesting a session from a display manager.

Not correct SSH X11 forwarding, and the objection is that the tunnel cannot carry a login screen.

Wrong on the first half. SSH forwarding is a genuinely good way to run remote X clients, and it is encrypted, but it presupposes that you have already logged in — which is exactly the step XDMCP performs.

Why

XDMCP is the query protocol between an X server and a display manager such as xdm, gdm or lightdm; the X server broadcasts or directly queries, the display manager replies and manages the session. It listens on UDP port 177 and is disabled by default on modern distributions precisely because it is unauthenticated and unencrypted. The encrypted alternative for running remote graphical applications is ssh -X, which forwards X clients over an already authenticated channel.

Where this comes from

Cited
manual page xdm(1)

Practise this

Reading one question is not practice. The trainer will draw a short set from objective 106 and space the ones you get wrong.

Practise LPIC-1 Exam 102-500

More questions on this objective

All questions on User interfaces and desktops

Practise LPIC-1 Exam 102-500