What technique could be used to investigate report performance?

Question

Options

• AIncrease the size limit for the user session.
• BReview the system metrics.
• CEnable the interactive performance assistant
• DEnable legacy user interface.

• A
  5% (1)
• B
  5% (1)
• C
  91% (20)

Explanation

Enabling the Interactive Performance Assistant (option C) is correct because it is a built-in diagnostic tool specifically designed to capture and analyze report execution details - such as query times, data fetch durations, and rendering steps - giving you targeted insight into where performance bottlenecks occur.

Why the distractors are wrong:

• A (Increase session size limit): This addresses memory allocation constraints for user sessions, not performance diagnostics - it won't tell you why a report is slow.
• B (Review system metrics): System metrics show general server health (CPU, memory, disk), but they lack report-level granularity needed to pinpoint a specific report's performance issue.
• D (Enable legacy UI): Switching to the legacy interface changes how the UI renders, not how performance is measured or investigated.

Memory tip: Think of the Interactive Performance Assistant as your personal report detective - it actively assists you in uncovering the specific steps causing slowness, unlike general tools (system metrics) that only show the big picture. If the question mentions "investigate" + "report performance," the dedicated assistant tool is almost always the answer.

No community discussion yet for this question.