BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe Exam AD0-E704 Topic 10 Question 48 Discussion

Actual exam question for Adobe's AD0-E704 exam
Question #: 48
Topic #: 10
[All AD0-E704 Questions]

You are working on a project where many catalog managers often change products in the admin panel.

The merchant is considering changing the indexers mode to "Update on Schedule" from "Update on Save" to achieve better performance. However, the merchant is concerned about data consistency and the probability of the scheduled updates being lost.

How does Magento store the IDs of updated products for reindex in "Update on Schedule" mode?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Reid at Sep 16, 2024, 02:26 PM

Limited Time Offer

25%

Off

Get Premium AD0-E704 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Cherelle
1 months ago
Haha, imagine if Magento just threw all the updated IDs into the Message Queue and then lost them all. What a mess that would be!
upvoted 0 times
...
Chantell
2 months ago
I'm not sure about the database triggers in D. Wouldn't that be a bit overkill for this use case?
upvoted 0 times
Celeste
12 days ago
I'm not sure about the database triggers in D. Wouldn't that be a bit overkill for this use case?
upvoted 0 times
...
Gearldine
19 days ago
B) Magento sets a reindex_required flag on updated products and a later reindex run by the cron will pick up IDs based on that flag.
upvoted 0 times
...
Kanisha
22 days ago
A) Magento is gathering updated IDs using catalog_product_save_commit_after events and publishes them into the Message Queue.
upvoted 0 times
...
...
Coletta
2 months ago
C seems plausible too, with the Staging update running every minute. That would keep the data consistent.
upvoted 0 times
Diane
14 days ago
C seems plausible too, with the Staging update running every minute. That would keep the data consistent.
upvoted 0 times
...
Adelaide
26 days ago
C) Using the Staging update scheduled for every minute, which includes modified products, Magento will automatically reindex affected products when the update is applied.
upvoted 0 times
...
Jolanda
27 days ago
B) Magento sets a reindex_required flag on updated products and a later reindex run by the cron will pick up IDs based on that flag.
upvoted 0 times
...
Cherrie
1 months ago
A) Magento is gathering updated IDs using catalog_product_save_commit_after events and publishes them into the Message Queue.
upvoted 0 times
...
...
Luisa
2 months ago
I'm not sure, but I think C) Using the Staging update scheduled for every minute, which includes modified products, Magento will automatically reindex affected products when the update is applied, makes sense too.
upvoted 0 times
...
Corinne
2 months ago
I think the answer is B. The reindex_required flag on updated products sounds like the most efficient way to keep track of which products need to be reindexed.
upvoted 0 times
Jettie
1 months ago
That makes sense. It seems like a simple and effective way to manage reindexing.
upvoted 0 times
...
Maia
1 months ago
B) Magento sets a reindex_required flag on updated products and a later reindex run by the cron will pick up IDs based on that flag.
upvoted 0 times
...
...
Georgeanna
2 months ago
I disagree, I believe the correct answer is B) Magento sets a reindex_required flag on updated products and a later reindex run by the cron will pick up IDs based on that flag.
upvoted 0 times
...
Celeste
2 months ago
I think the answer is A) Magento is gathering updated IDs using catalog_product_save_commit_after events and publishes them into the Message Queue.
upvoted 0 times
...

Save Cancel