New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe AD0-E716 Exam - Topic 8 Question 55 Discussion

Actual exam question for Adobe's AD0-E716 exam
Question #: 55
Topic #: 8
[All AD0-E716 Questions]

An international merchant is complaining that changes are taking too long to be reflected on the frontend after a full product import.

Thinking it may be database issues, the Adobe Commerce developer collects the following entity counts:

* Categories: 900

* Products: 300k

* Customers: 700k

* Customer groups : 106

* Orders: 1600k

* Invoices: 500k

* Creditmemos: 50k

* Websites : 15

* Stores : 45

What is a probable cause for this?

Show Suggested Answer Hide Answer
Suggested Answer: C

The probable cause for the delay in reflecting the changes on the frontend after a full product import is the combination of the number of products, customer groups and websites. 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. The price index calculates the final price of each product for each customer group and website, taking into account various factors such as tax, discounts, catalog price rules, etc. When there are many products, customer groups and websites, the price index becomes very complex and time-consuming to update. Verified Reference: [Magento 2.4 DevDocs] [Magento Stack Exchange]


Contribute your Thoughts:

0/2000 characters
Tiara
5 days ago
I’m not entirely sure, but could it be related to indexing? I think we practiced a question about that.
upvoted 0 times
...
Merissa
10 days ago
I remember we discussed how large product databases can slow down frontend updates, especially with 300k products.
upvoted 0 times
...
Leonardo
16 days ago
This is a tough one, but I've dealt with similar issues before. My first step would be to profile the database and identify any bottlenecks or performance hotspots. Then I can start optimizing from there.
upvoted 0 times
...
Lai
21 days ago
Okay, let's break this down. With that many entities, I'm thinking the database might be struggling to keep up. Indexing, partitioning, and maybe even sharding could be worth exploring.
upvoted 0 times
...
Thea
26 days ago
Hmm, 300k products and 700k customers? That's a huge amount of data to manage. I'd start by checking the database indexes and see if we can optimize some of the queries.
upvoted 0 times
...
Izetta
1 month ago
Whoa, that's a lot of data! I'm guessing the sheer volume of products, customers, and orders is causing some serious performance issues. Might need to look at indexing and caching strategies.
upvoted 0 times
...
Laura
1 month ago
This sounds like a complex issue with a lot of data to consider. I'll need to think through the different database entities and how they might be impacting performance.
upvoted 0 times
...

Save Cancel