Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E703 Topic 5 Question 72 Discussion

Actual exam question for Adobe's AD0-E703 exam
Question #: 72
Topic #: 5
[All AD0-E703 Questions]

You are creating a new indexer which must run after the targetrule_product_rule index process. When you run bin/magento indexer:reindex, your rule always runs first creating inaccurate dat

a. What is the resolution?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Ricki
2 months ago
I bet the person who came up with this question has had some real fun debugging Magento indexers in the past. Option A for me!
upvoted 0 times
...
Sharen
2 months ago
Creating a bash script to execute each indexer in the correct order seems like a feasible solution as well.
upvoted 0 times
...
Mollie
2 months ago
Ah, the joys of Magento indexing! Option B all the way - keep it simple and straightforward.
upvoted 0 times
...
Destiny
2 months ago
D is a bit hacky, I don't think I'd want to rely on a bash script for this. I'd choose one of the configuration options.
upvoted 0 times
Mariann
26 days ago
C) Use a plugin on the IndexManager class to change load order.
upvoted 0 times
...
Shaun
29 days ago
B) Specify the sortOrder in your indexer configuration.
upvoted 0 times
...
Ettie
2 months ago
A) Use a dependencies node in your indexer configuration.
upvoted 0 times
...
...
Thersa
2 months ago
Option C is interesting, but a plugin might be overkill for this. I'd stick with the indexer configuration.
upvoted 0 times
...
Ligia
2 months ago
I'd go with Option A. Using the dependencies node is a cleaner approach than a plugin or a bash script.
upvoted 0 times
Janey
26 days ago
User4: Option A it is then!
upvoted 0 times
...
Barbra
27 days ago
User3: I always prefer cleaner solutions.
upvoted 0 times
...
Maryrose
28 days ago
User2: I agree, using the dependencies node is cleaner.
upvoted 0 times
...
Carli
1 months ago
User1: I think Option A is the best solution.
upvoted 0 times
...
...
Sommer
3 months ago
Option B seems like the way to go. The sortOrder should let you control the order of execution for the indexers.
upvoted 0 times
Paulina
19 days ago
Option B seems like the way to go. The sortOrder should let you control the order of execution for the indexers.
upvoted 0 times
...
Dahlia
20 days ago
B) Specify the sortOrder in your indexer configuration.
upvoted 0 times
...
Mitzie
22 days ago
A) Use a dependencies node in your indexer configuration.
upvoted 0 times
...
Thersa
26 days ago
C) Use a plugin on the IndexManager class to change load order.
upvoted 0 times
...
Tammi
1 months ago
A) Use a dependencies node in your indexer configuration.
upvoted 0 times
...
Val
1 months ago
B) Specify the sortOrder in your indexer configuration.
upvoted 0 times
...
...
Cassandra
3 months ago
I believe using a plugin on the IndexManager class to change load order could also work.
upvoted 0 times
...
Tracey
3 months ago
I agree with Johnna, specifying the sortOrder in the indexer configuration should solve the issue.
upvoted 0 times
...
Johnna
3 months ago
I think the resolution is to use a dependencies node in the indexer configuration.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77