1D0-541 · Question #120
A large enterprise uses a two-tier database architecture and runs complex database processing on the client. Which term best describes the client in this system?
The correct answer is A. Fat client. See the full explanation below for the reasoning.
Question
A large enterprise uses a two-tier database architecture and runs complex database processing on the client. Which term best describes the client in this system?
Options
- AFat client
- BThin client
- CTerminal client
- DEnterprise client
How the community answered
(29 responses)- A76% (22)
- B3% (1)
- C14% (4)
- D7% (2)
Community Discussion
6
Fatima Z.Nov 27, 2025The answer is A, Fat client, and here is the sticky way to lock it in. Picture a client machine that had one too many slices of pizza, it is carrying all that heavy processing weight on its own plate. In a two-tier architecture the client tier and the server tier split the work, and when complex database logic runs on the client side, that machine is doing the heavy lifting, which is exactly what makes it FAT, short for Full Application Tier. A thin client would push that work up to the server and just display results, basically a screen with a keyboard, but a fat client owns the processing and talks directly to the database server for data. So whenever you see "runs complex processing on the client," picture the overstuffed pizza guy and bubble up FAT CLIENT every single time.
Imani T.Nov 29, 2025FAT in "fat client" is not actually an acronym for Full Application Tier, that is a backronym that floats around study guides but the term just comes from the idea of a resource-heavy client compared to a lightweight thin client.
Imani T.Dec 14, 2025A is the right call here. In a two-tier setup the client talks directly to the database server, and when complex processing happens on that client side, it has to carry the weight of business logic, data manipulation, and presentation all at once. That is the textbook definition of a fat client, sometimes called a thick client, because the machine doing the work needs real compute power and usually has a full application stack installed locally. Thin clients offload that work to a server and just handle display, which is the opposite of what this question is describing.
Mei-Ling H.Dec 16, 2025Good call on A, but the qualifier doing the real work is "complex processing on the client side," because two-tier alone does not lock in fat client, you could have a two-tier setup with a thin client if the server handles the logic.
Mei-Ling H.Nov 29, 2025The question says "complex database processing on the client" and a two-tier architecture, so the client is doing heavy lifting, but I keep coming back to C because in legacy enterprise setups the term "terminal client" often referred to the workstation that connected directly to the database server and handled processing locally, which matches the two-tier description exactly. The word "terminal" in older CIW documentation points to the endpoint that sits at the client tier and executes queries, so C feels like the right fit here.
Fatima Z.Nov 30, 2025Mei-Ling, the giveaway is the phrase "complex processing on the client," which is the whole definition of a fat client (think FAT = Functions Are There, on the client side). A terminal is actually the opposite, it is a thin device that ships work off to the server, so C flips the processing location exactly backwards from what the question describes.