Comprehensive and Detailed Explanation From Exact Extract:

Pega’s reporting capabilities, as taught in Pega Academy’sReporting Missionand thePega Certified Lead System Architect Study Guide, provide tools like function aliases to categorize data efficiently in reports. For grouping customers by shopping history duration, a function alias is the most straightforward and performant approach.

Option A (Correct): A function alias allows categorization of shopping history into buckets (e.g., >10 years, 5–10 years) using a calculated field in a Report Definition. This is efficient, reusable, and aligns with Pega’s best practices for dynamic reporting, as documented in theReport Definition Configurationsection of Pega Community.

Option B (Incorrect): A correlated subreport is complex and resource-intensive, requiring multiple queries to correlate data. It is overkill for simple categorization, per theReporting Designmodule.

Option C (Incorrect): Using a Rule-Obj-ListView with a custom getContent activity is outdated and less flexible than modern Report Definitions. ListViews are deprecated in favor of Report Definitions, as noted in theLegacy Reportingguidelines.

Option D (Incorrect): A Connect-SQL rule bypasses Pega’s reporting framework, reducing maintainability and security. Report Definitions with function aliases are the recommended approach, per theReport Definitionmodule.