System Architecture and Reliability

Which describes a thin client?

  1. AAn approach in which users' terminals have a high-performance CPU and large storage so that they can process on their own even without a network connection
  2. BAn approach that minimizes the terminal's functions while letting the terminal alone continue the work even if the network is cut off
  3. CAn approach in which users' terminals have only minimal functions such as input and output, and applications are run and data is stored on the server side
Show answer and explanation

Answer: C. An approach in which users' terminals have only minimal functions such as input and output, and applications are run and data is stored on the server side

A thin client gives the terminal only minimal functions such as input and screen display, and runs applications and stores data on the server side. Because no data remains on the terminal, information leaks from lost or stolen terminals are easier to prevent, and software can be updated centrally on the server side. In exchange, work cannot continue on the terminal if the network or server stops. An approach in which the terminal itself does much of the processing is called a fat client (rich client).

  • A. This describes a fat client (rich client).
  • B. A thin client processes on the server, so work cannot continue if the network is cut off.
  • C. Correct. Processing and data are gathered on the server, and the terminal only handles input and output.
Practice this topic Back to topic

Related calculators

Books on System Architecture and Reliability Ad

As an Amazon Associate I earn from qualifying purchases.

More System Architecture and Reliability questions

  1. Which is a characteristic of a peer-to-peer (P2P) system?
  2. Which is a characteristic of distributed processing compared with centralized processing?
  3. Which task is suited to batch processing?
  4. Among the measures used to evaluate the performance of an online processing system, which describes response time?
  5. In a system, each user request is processed in order by a web server tier, an application server tier and a database server tier. Each request passes through each of the three tiers once, and the maximum number of requests each tier can process is 1,200 per second for the web server tier, 1,000 per second for the application server tier and 900 per second for the database server tier. If the database server tier is upgraded to process 1,500 per second, which is the maximum number of requests the whole system can process?