AD0-E716: Adobe Commerce Developer with Cloud Add-on ExpertDemo

By Adobe · Question Mode

QuestionQ18

Working with Databases and EAV

An international merchant reports that, after a full product import, changes take too long to appear on the frontend.

Suspecting database issues, the Adobe Commerce developer gathers these entity counts:

  • Categories: 900
  • Products: 300k
  • Customers: 700k
  • Customer groups: 106
  • Orders: 1600k
  • Invoices: 500k
  • Creditmemos: 50k
  • Websites: 15
  • Stores: 45

What is a likely cause?

  • A The combination of the number of products, categories and stores is too big. This leads to a huge amount of values being stored in the flat catalog indexes which are too large to be processed at a normal speed.
  • B The combination of the number of orders, customers, invoices and creditmemos is too big. This leads to a huge amount of values being stored in the customer grid index which is too large to be processed at a normal speed.
  • C The combination of the number of products, customer groups and websites are too big. This leads to a huge amount of values being stored in the price index which is too large to be processed at a normal speed.
Explanation

The product price index has a potentially massive product × customer-group × website scope. Here, 300,000 products across 106 customer groups and 15 websites can yield roughly 477 million combinations to index, making full product-import reindexing slow. Adobe Commerce documentation specifically warns that many products, websites, and customer groups increase product-price indexing time.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!