MENU
A client reports an issue with indexers that are failing and remain stuck. The client asks a Developer to solve this issue.
What recommended solution should the Developer use?
Suggested Answer: B
Get Premium AD0-E725 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
JE
Jeff
7 months ago
Let's go with C then.
MA
Margarita
7 months ago
Exactly! Plus, it keeps everything updated instantly.
JE
Jeff
7 months ago
I feel like C gives more control over indexing.
MA
Margarita
8 months ago
Right, disabling sync mode isn't ideal.
JE
Jeff
8 months ago
Good point. B seems risky, could lead to more problems.
MA
Margarita
8 months ago
True, but it might not fix the root issue.
JE
Jeff
8 months ago
I agree, but A could help automate the process too.
MA
Margarita
8 months ago
I think option C is the best. Real-time indexing is crucial.
AN
Andra
9 months ago
I’m surprised people still use cronjobs for this.
SO
Sommer
9 months ago
Wait, does anyone really think B is a good idea?
FE
Felix
9 months ago
C is the best for real-time updates, no doubt!
BE
Bernadine
9 months ago
I disagree, B could lead to issues if not monitored.
TA
Tanesha
9 months ago
I’ve seen similar questions where setting the indexer to realtime was the answer, but I wonder if that would really fix the issue in this case.
BR
Brendan
9 months ago
I feel like option B, changing the sync mode in env.php, could help, but I’m not entirely confident about the implications of that change.
AN
Anika
10 months ago
I think option A could be a good solution, but I'm not sure if running a cronjob is the best way to handle stuck indexers.
VI
Vilma
10 months ago
Option C is the way to go, but I'd also recommend a nice cold beer to celebrate fixing those pesky indexers.
FR
France
10 months ago
Option A is a solid choice for periodic reindexing.
JE
Jenifer
10 months ago
I remember practicing a question about setting the indexer mode to realtime. That might be option C, but I can't recall if it's the right choice here.
DW
Dwight
11 months ago
Haha, a cronjob? What is this, the Stone Age? Option C is the clear winner here.
BI
Billy
11 months ago
Cronjob? Really? That's so 2010. Option C is the future, my friend.
FR
France
11 months ago
I'd go with option B. Setting the indexer_sync_mode to false should help with the issue.
LA
Lachelle
11 months ago
Option C is the way to go. Reindexing in real-time is the best solution to fix those stuck indexers.
CH
Chauncey
12 months ago
I'm leaning towards option C. Putting the indexers in realtime mode should keep them up-to-date and prevent the issue from recurring. It's a more proactive solution than just trying to reindex periodically.
CI
Ciara
12 months ago
Option B seems risky to me - disabling the indexer sync mode could lead to data inconsistencies. I'd be cautious about trying that without fully understanding the implications.
CH
Cherrie
12 months ago
Option A with a cronjob could work, but I'm not sure if that's the best long-term solution. It might just be masking the underlying issue.
VI
Virgina
1 year ago
Hmm, this is a common issue we've seen before. I think option C might be the best approach here - setting the indexers to realtime mode should help prevent them from getting stuck.
ER
Eric
1 year ago
I'm not sure about this one, the question seems a bit tricky. I'll need to carefully read through the options and think about the potential consequences of each approach.
RE
Reyes
6 months ago
I prefer option C. Real-time indexing seems more efficient.
YA
Yasuko
6 months ago
But what about option B? Disabling sync mode might help too.
CA
Carey
6 months ago
I think option A is safe. Regular reindexing could prevent issues.
OL
Olive
10 months ago
True, but we need to consider the server load with real-time updates.