A developer recently created a new criterion for the recommendation service. After implementing a Recommendations Activity using the new criterion, the developer is unable to view the…

Question

Options

• AThe Activity is targeting the wrong pages.
• BResults are not yet cached at the nearest Edge server.
• CThe Design contains an error.
• DThe recommendation criteria is unsupported.

• A
  3% (1)
• B
  75% (24)
• C
  6% (2)
• D
  16% (5)

Explanation

Option B is correct because no_content specifically indicates the results exist at the origin but have not yet propagated to the nearest Edge server - the CDN node closest to the user. Even when an algorithm has fully computed results for a given key, there is a caching/propagation delay before those results are available at the edge, so the system returns no_content rather than serving stale or missing data.

Why the distractors are wrong:

• A - Targeting the wrong pages would serve incorrect recommendations or nothing contextually relevant, but wouldn't produce no_content on its own; the results themselves are confirmed ready.
• C - A Design error would surface as a configuration or rendering problem, not a no_content status, and the question already confirms the algorithm/key combination is valid.
• D - If the criterion were unsupported, results would never be ready - but the question explicitly states results are ready, ruling this out.

Memory tip: Think "baked but not delivered" - no_content means the result is cooked (algorithm is done), but the delivery truck (Edge cache) hasn't picked it up yet. Edge propagation delay = no_content.

No community discussion yet for this question.