PEGACPLSA23V1 practice question 2 of 15

[Reporting Design] In a retail inventory management application, the system captures and stores product sales data in the backend database to manage…

Full set: 60 questions
[Reporting Design] In a retail inventory management application, the system captures and stores product sales data in the backend database to manage inventory levels effectively. The organization requires a comprehensive report to analyze product sales trends over the past 5 years, including details on which products sold the most and least, and their corresponding profit margins. As a Lead System Architect, which well-designed solution do you suggest for implementing this requirement?
Answer options
A: Segment the product-related data into a CustomerData schema and sales workflow data into the PegaDATA schema within the database. Utilize Business Intelligence Exchange rules to extract this data daily, then store it in a dedicated data warehouse for analysis with specialized Business Intelligence tools.
B: Partition the product-related data in the CustomerData schema and the sales workflow data in the PegaDATA schema within the database. Provide access to these schemas for specialized Business Intelligence tools to directly query and analyze the data.
C: Store both product-related data and sales workflow data in the PegaDATA schema within the database. Use Business Intelligence Exchange rules to extract this data daily and transfer it to a designated data warehouse for analysis with specialized Business Intelligence tools. Correct answer
D: Centralize both product-related data and sales workflow data in the CustomerDataschema within the database, optimizing the necessary properties for efficient querying. Grant access to this schema to specialized Business Intelligence tools to perform in-depth analysis.
Correct Answer:
C. Store both product-related data and sales workflow data in the PegaDATA schema within the database. Use Business Intelligence Exchange rules to extract this data daily and transfer it to a designated data warehouse for analysis with specialized Business Intelligence tools.
Explanation

This solution represents the most robust and scalable architectural pattern for handling large-scale historical reporting in Pega. Storing all application-related data, including product master data and transactional sales data, within the standard PegaDATA schema is the correct approach. For complex, long-term trend analysis spanning five years, using Business Intelligence Exchange (BIX) to extract data to a dedicated data warehouse is the Pega-recommended best practice. This strategy offloads resource-intensive analytical queries from the live transactional database, preventing performance degradation of the core application while enabling powerful analysis with specialized BI tools.

Why Incorrect

A: Incorrectly suggests segmenting product data into the CustomerData schema. Product data is core application data and belongs in the PegaDATA schema alongside the related sales workflow data. B: Proposing direct queries by BI tools on the live transactional database is a significant anti-pattern that would severely impact the application's performance, especially with five years of data. D: Incorrectly centralizes all data in the CustomerData schema and recommends direct database querying by BI tools, which is both an incorrect data model and a poor performance strategy.

References

1. Pega Academy (Lead System Architect 8.7 Module): "BIX and data extraction". This module explicitly details the use of Business Intelligence Exchange (BIX) for extracting large volumes of data from the Pega database to a separate reporting database or data warehouse. It emphasizes this approach to avoid performance impacts on the transactional system when running complex, long-running reports. The scenario in the question is a classic use case for BIX.

2. Pega Documentation: "Business Intelligence Exchange (BIX)". The official documentation describes BIX as the tool for extracting transactional data from the Pega Platform database into formats suitable for use in external reporting, analytics, and data warehousing systems. It highlights that BIX is designed for high-performance extraction without impacting OLTP users.

3. Pega Documentation: "Understanding the Pega Platform schemas". This documentation clarifies the purpose of the different schemas. The PegaDATA schema is the primary schema for all case data, assignments, and application-specific data tables. The CustomerData schema is designated for customer-centric data, typically used by Pega Marketing and Customer Service applications, not for general application or product master data. Storing both product and sales data in PegaDATA is the standard practice.

Scroll to Top