In a retail inventory management application, the system captures and stores product sales data in...

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s reporting and data integration capabilities, as outlined in Pega Academy’sReporting Missionand thePega Certified Lead System Architect Study Guide, recommend using Business Intelligence Exchange (BIX) for extracting large datasets to external data warehouses for advanced analytics. This ensures performance and scalability for historical trend analysis.

Option A (Incorrect): Segmenting product data into a CustomerData schema and sales data into PegaDATA is unnecessary and complicates data management. PegaDATA is the standard schema for Pega application data, and splitting schemas does not align with BIX best practices, per theBIX Configurationmodule.

Option B (Incorrect): Directly querying PegaDATA and CustomerData schemas with BI tools can degrade application performance due to heavy database load. Pega recommends offloading analytics to a data warehouse via BIX, as noted in theReporting Designguidelines.

Option C (Correct): Storing both product and sales data in the PegaDATA schema (Pega’s default schema) and using BIX rules to extract data daily to a data warehouse is optimal. This approach minimizes application impact, supports scalable analytics with BI tools, and aligns with Pega’s best practices, as documented in theBusiness Intelligence Exchangesection of Pega Community.

Option D (Incorrect): Centralizing data in a CustomerData schema and optimizing for direct BI tool queries risks performance issues in the Pega database. BIX extraction to a data warehouse is the preferred method, per theData Warehouse Integrationmodule.