Comprehensive and Detailed Explanation From Exact Extract:

Pega’s data modeling and performance optimization principles, as taught in Pega Academy’sData Modeling MissionandLead System Architect Mission, recommend using separate data pages for hierarchical data to ensure modularity, scalability, and efficient data retrieval. For a category-subcategory navigation system, data pages should be structured to reflect the hierarchy and dependency between categories and sub-categories.

Option A (Incorrect): Using a single data page that accepts either a Category or Sub-category as a parameter is overly complex and violates Pega’s principle of modular design. It requires conditional logic to handle different parameter types, which reduces maintainability and clarity, as noted in theData Page Designmodule.

Option B (Incorrect): Loading Categories by default and using a single Sub-category data page is partially correct but incomplete. It does not explicitly define a separate data page for Categories, which could lead to inefficiencies inmanaging the category list independently. Pega recommends distinct data pages for each level of a hierarchy, per theData Modelingguidelines.

Option C (Correct): Implementing separate data pages for Categories and Sub-categories, with the Sub-category data page taking the Category as a parameter, is the best approach. This modular design allows the Category data page to load the list of categories and the Sub-category data page to dynamically fetch sub-categories based on the selected category. This aligns with Pega’s best practices for hierarchical data retrieval, as outlined in theData Pagesmodule.

Option D (Incorrect): Using a single data page that takes only the Sub-category as a parameter assumes sub-categories can be accessed independently, which ignores the dependency on categories. This approach is inefficient and does not support the hierarchical navigation required, per Pega’sData Modeling Mission.