A retailer is experiencing issues where their product recommendations do not show during high traffic periods. What should the architect check first?

Question

Options

• AValidate server performance and scalability
• BVerify catalog feed update intervals
• CDebug audience segment mapping
• DMonitor at.js script performance

• A
  85% (33)
• B
  3% (1)
• C
  5% (2)
• D
  8% (3)

Explanation

Option A is correct because the issue is explicitly tied to high traffic periods, which is a classic indicator of a server-side capacity or scalability bottleneck - if the recommendation engine can't handle concurrent requests under load, it will fail to serve results regardless of configuration. Option B (catalog feed intervals) is wrong because feed update timing is a data freshness concern unrelated to traffic volume. Option C (audience segment mapping) is a targeting logic issue that would cause incorrect or missing recommendations regardless of traffic, not specifically during peak load. Option D (at.js performance) is a client-side concern that could contribute to display issues but wouldn't explain a pattern tied specifically to high traffic - server infrastructure fails under load, not browser scripts.

Memory tip: Think "traffic spike = server spike." Whenever a problem is traffic-correlated, always look at infrastructure and scalability first before debugging configuration, data feeds, or client-side code.

No community discussion yet for this question.