Comprehensive and Detailed Explanation From Exact Extract:

Pega’s data modeling best practices, as outlined in Pega Academy’sData Modeling Missionand thePega Certified Lead System Architect Study Guide, emphasize designing data models that promote reuse, maintainability, and efficient data propagation. In a case hierarchy, the parent-child case relationship is ideal for sharing common data, with the parent case storing shared attributes and propagating them to child cases to avoid redundancy.

Option A (Correct): Setting Schedule Flight as the parent case type with pre-flight check and flight catering as child case types is optimal. Storing flight data (e.g., flight number, cabin class) in the Schedule Flight case allows this data to be propagated to child cases upon creation, ensuring consistency and reducing duplication. Pega’s case management framework supports data propagation from parent to child cases, making this a straightforward and maintainable approach, as described in theCase Designmodule.

Option B (Incorrect): Placing flight data in the travel management enterprise layer and having child case types inherit from it introduces unnecessary complexity. The enterprise layer is meant for reusable, organization-wide data, not case-specific data like flight details. This approach violates Pega’s principle of keeping case-specific data within the case hierarchy, as noted in theData Modelingguidelines.

Option C (Incorrect): While the parent-child structure is correct, placing flight data in the Schedule Flight class and developing separate data classes for each child case type is redundant. Child cases can inherit or propagate data directly from the parent case, eliminating the need for separate data classes unless unique attributes are required. This approach overcomplicates the data model, per Pega’sData Modeling Mission.

Option D (Incorrect): Storing flight data in the work pool class (a higher-level class like Work-) is inappropriate because work pool classes are meant forgeneric, application-wide properties, not case-specific data. This would lead to poor data organization and potential conflicts across case types, contradicting Pega’s data modeling best practices.