An AEM client requests that an Architect to establish non-functional KPIs. The Architect needs to avoid impacting user experience, asset processing, and download speed while doing this. How should…

Question

Options

• ATail the Access Log and look for long-running queries
• BUse the Free Request Log Analyzer Command Line Tool
• CUse JMeter for end-to-end tests
• DUse the OOTB Explain Query Tool

• A
  11% (3)
• B
  4% (1)
• C
  7% (2)
• D
  79% (22)

Explanation

Using the OOTB (Out-of-the-Box) Explain Query Tool in AEM allows the Architect to analyze Oak/JCR query execution plans and identify performance bottlenecks without generating additional load on the system, making it the only option that satisfies the constraint of not impacting user experience, asset processing, or download speed. Option C (JMeter) is wrong because end-to-end load testing actively generates traffic and stress on the system, directly impacting the very metrics you're trying to protect. Options A and B (tailing the access log and the Request Log Analyzer) are reactive, post-hoc analysis tools - they tell you what already happened rather than helping you proactively establish target KPIs in a controlled, non-invasive way. The Explain Query Tool gives you a structured, diagnostic view of how queries will perform, which is exactly what's needed to define measurable baselines.

Memory tip: Think "Explain before you strain" - the Explain Query Tool lets you analyze queries without executing them under load, keeping your environment clean while you set your KPI targets.

No community discussion yet for this question.