Difficulty: Easy
Correct Answer: Does not apply — a fat client usually includes significant local storage
Explanation:
Introduction / Context:
Client classifications describe how much work and data reside on the user device. A “fat client” (also called thick client) performs substantial processing locally and commonly stores data/configuration locally. A “thin client” minimizes local state and computation, relying heavily on servers.
Given Data / Assumptions:
Concept / Approach:
The statement claims fat clients have no or limited local storage, which conflates fat with thin clients. In practice, fat clients leverage local CPU/GPU and disk/flash to improve responsiveness, enable offline capability, and reduce server load.
Step-by-Step Solution:
Identify fat client traits: rich UI, local processing, local storage.Contrast with thin client traits: lightweight UI, server-side processing, minimal local data.Evaluate the statement: it describes thin clients, not fat clients.Therefore, the claim does not apply.
Verification / Alternative check:
Examples: full-featured desktop accounting software or CAD tools store significant local data and perform intensive processing — classic fat clients. Browser-based SaaS with minimal local storage aligns with thin clients.
Why Other Options Are Wrong:
Option b restates the incorrect definition. Options c and d misclassify thin/browser or VDI models as fat clients. Option e is incorrect; fat clients, by definition, execute logic locally.
Common Pitfalls:
Mislabeling clients can lead to poor architecture choices: e.g., assuming offline capability where none exists, or underestimating server load for thin clients.
Final Answer:
Does not apply — a fat client usually includes significant local storage
Discussion & Comments