Which of the following is a disadvantage of thick-client based solution?
-
Provides very good client security, persons without a client cannot access system.
-
Ability to access the client's PC utilities or Native API's.
-
Maintainability of application code is good.
-
UI changes are easily and immediately available to the clients.
Thick clients require software installation and updates on each user's machine. When UI changes are made, they must be packaged and redeployed to all clients - a complex, time-consuming process. In contrast, web-based applications update instantly on the server. Option D describes an advantage of web/thin clients, which by comparison is a disadvantage of thick clients.
This option is awkwardly worded, but the intended point is about UI/deployment maintenance: true thick-client disadvantages are that any UI or logic change must be repackaged and redeployed to every client machine individually — updates are NOT easily or immediately available, unlike a thin/web client where server-side changes reach all users instantly. The other options (good client-side security, access to native PC APIs) are actual thick-client advantages, so they're rightly excluded. The marked answer's literal phrasing ("UI changes are easily and immediately available") reads as a benefit rather than a drawback, which suggests the option was intended to be read as describing what does NOT hold true for thick clients — i.e., a reversed/shorthand way of flagging the deployment-lag disadvantage.