A developer observes that after updating a product's name in the Adobe Commerce admin, the change is not immediately reflected in the associated SaaS-based Live Search results. The system is configure

Question

Options

• AThe Live Search service is disconnected and needs new API keys to be configured.
• BThe product update must be approved in the SaaS platform's admin console first.
• CThe change is waiting for the Full Sync, which only runs weekly.
• DThe change is queued for a Partial Sync, which is triggered by a periodic cron job.

• A
  11% (3)
• B
  26% (7)
• C
  4% (1)
• D
  59% (16)

Explanation

When a product attribute like a name is updated in Adobe Commerce, the change is not pushed to Live Search instantly - instead, it is queued as a Partial Sync, which runs on a scheduled cron job (typically every few minutes). This is the expected, standard behavior of the SaaS data export pipeline that feeds Live Search, and the brief lag is by design, not a sign of misconfiguration.

Why the distractors are wrong:

• A is wrong because a disconnected service or missing API keys would cause search to fail entirely, not merely delay updates.
• B is wrong because no approval workflow exists in the Live Search SaaS console for individual product changes - that's not how the platform works.
• C is wrong because Full Sync (which reindexes all catalog data) is not weekly; it is triggered manually or on initial setup, while routine updates use Partial Sync.

Memory tip: Think of it as a postal system - small updates (Partial Sync) go out in scheduled batches like daily mail runs, while a Full Sync is like moving the entire post office. The cron job is the mail carrier that picks up the queue on a schedule.

No community discussion yet for this question.