Which description accurately captures a feature of N-tier architecture?

Which description accurately captures a feature of N-tier architecture?

• A. It is expandable to multiple web servers and application servers to handle load balancing; web servers can be geographically dispersed.
• B. It is limited to a single web server and a database.
• C. It requires duplicate data storage on each tier.
• D. It relies exclusively on client-side processing.

Answer: (A)

N-tier architecture is built to scale by spreading components across multiple servers and locations, with distinct layers handling presentation, business logic, and data access. This setup supports expanding the system by adding more web and application servers behind load balancers, and those servers can be placed in different geographic regions to improve performance and resilience. That’s why describing it as expandable to multiple web servers and application servers for load balancing, with geographically dispersed web servers, best captures how N-tier systems operate. The other descriptions don’t fit this pattern: relying on a single web server and database reflects a non-scalable setup; requiring duplicate data storage on each tier isn’t an inherent requirement of N-tier architecture; and leaning on client-side processing misses the server-side layers that define N-tier design.

N-tier architecture is built to scale by spreading components across multiple servers and locations, with distinct layers handling presentation, business logic, and data access. This setup supports expanding the system by adding more web and application servers behind load balancers, and those servers can be placed in different geographic regions to improve performance and resilience. That’s why describing it as expandable to multiple web servers and application servers for load balancing, with geographically dispersed web servers, best captures how N-tier systems operate.

The other descriptions don’t fit this pattern: relying on a single web server and database reflects a non-scalable setup; requiring duplicate data storage on each tier isn’t an inherent requirement of N-tier architecture; and leaning on client-side processing misses the server-side layers that define N-tier design.