posted 8 years ago
I disagree.
A two-tier system can have a thin client as well, if the business logic is implemented in the database. Even though in most cases a two-tier system has a thick client, it is not a given. Thus, A, to me, is not correct, because of the use of the term "always". In fact, in a two-tier system I would prefer to have the business logic in the DB.
However, it is far easier to manage a three tier system than a two tier system IMO. How do you monitor all your clients? How do you redeploy or upgrade? I would like to meet the person that thinks a mandatory client upgrade is easier than an application redeploy. In a 3-tier system you can leverage JMX for optimized application management. In a 2-tier system, forget about it.
Security I would also give to 3-tier, but that really depends on the scenario.
But B and E I would definitely consider true.
Oracle Certified Professional: Java SE 6 Programmer && Oracle Certified Expert: (JEE 6 Web Component Developer && JEE 6 EJB Developer)