Expanding an Adobe Commerce instance by adding websites, SKUs, and customer groups introduces significant scalability challenges. The platform's EAV (Entity-Attribute-Value) model stores attribute values at different scopes (global, website, store view). Adding new websites for different countries necessitates website-scoped attributes (e.g., price, tax class), which directly increases the size of catalog data tables (B). This data growth, combined with more stores, directly impacts performance. The indexing process, which is crucial for frontend performance, will take longer as it must process data for each additional store. Consequently, database queries for non-cached pages become more complex and slower, leading to increased response times (C).

A. Recreate hierarchy navigation for every new website.

This is not a mandatory issue. A new website requires a root category, but you can create a new one or assign an existing one. The entire hierarchy does not necessarily need to be recreated.

D. Multiple websites may require duplicating custom functionality for each store, which increases code redundancy.

This describes poor development practice, not an inherent architectural issue. Well-designed modules are configured per website/store; the core code is not duplicated, thus avoiding redundancy.

1. Adobe Commerce Developer Documentation

"Performance Best Practices > Database optimization": This guide discusses the impact of catalog size on performance. It states

"The number of products has a direct impact on the catalog browsing performance... The number of websites

stores

and store views also affects performance because it relates to the number of scopes in your system." This supports that adding websites and SKUs (expanding the catalog) impacts performance

validating answers B and C.

2. Adobe Commerce Developer Documentation

"PHP Developer Guide > Architecture > Scopes": This section explains how data for entities like products and categories can be set at different scopes (global

website

store view). It details how website-level scope allows for different pricing or product availability per website

which directly leads to an expansion of catalog data as new websites are added. This validates answer B.

3. Adobe Commerce Developer Documentation

"PHP Developer Guide > Indexing": The documentation explains

"Each indexer can perform one of the following reindex types: Full reindex... Partial reindex...". A larger catalog with more stores and SKUs increases the amount of data to be processed during both full and partial reindexing

making the process longer. This directly supports answer C.