A developer is trying to determine why an indexer is running every time a specific entity is saved in the Admin, causing a slight delay. They would prefer this index to run on a schedule. Which two…

The correct answer is D. Update on Save E. Update by Schedule. Adobe Commerce indexers operate in exactly two modes: Update on Save (D) and Update by Schedule (E). "Update on Save" triggers the indexer immediately whenever an entity is saved - which is exactly the behavior the developer is experiencing and wants to change. "Update by…

Administering

Question

A developer is trying to determine why an indexer is running every time a specific entity is saved in the Admin, causing a slight delay. They would prefer this index to run on a schedule. Which two modes can an Adobe Commerce indexer operate in? (Choose 2.)

Options

AUpdate Manually
BUpdate on Demand
CUpdate in Real-time
DUpdate on Save
EUpdate by Schedule

How the community answered

(28 responses)

A
4% (1)
C
4% (1)
D
93% (26)

Explanation

Adobe Commerce indexers operate in exactly two modes: Update on Save (D) and Update by Schedule (E). "Update on Save" triggers the indexer immediately whenever an entity is saved - which is exactly the behavior the developer is experiencing and wants to change. "Update by Schedule" queues index changes and processes them via a cron job, reducing real-time delays.

The distractors are fabricated: Update Manually (A), Update on Demand (B), and Update in Real-time (C) are not actual indexer modes in Adobe Commerce - they sound plausible but don't exist in the platform's indexer configuration UI or documentation.

Memory tip: Think "Save now or Schedule later" - there are only two choices, and the developer's problem (delay on save) literally names one of them. If the question mentions a schedule or cron, that's always the answer the developer wants to switch to.

Topics

#indexer modes#Update on Save#Update by Schedule#indexing

Community Discussion

No community discussion yet for this question.

Full AD0-E724 Practice