A shared catalog with reusable product-modeling components best satisfies both the enterprise governance objective and the distinct requirements of individual lines of business. Revenue Management allows reusable products, classifications, attributes, categories, selling models, and bundle components to be combined into business-specific offerings without unnecessarily duplicating the underlying commercial definitions.
During discovery, the architect should therefore identify common product capabilities first, establish reusable modeling patterns, and then determine where business-unit-specific rules, selling models, configurations, and approvals genuinely differ. This reduces SKU proliferation, improves consistency, and enables cross-selling because offerings are based on a governed commercial model rather than isolated product structures.
Option B would encourage each business unit to create independent bundles, producing redundant components and fragmented governance. Option C similarly introduces multiple catalogs as the default architecture even though executive stakeholders explicitly want unified governance and reuse. Multiple catalogs can be justified where genuinely distinct commercial boundaries exist, but they should not be used merely to isolate every business-unit variation.
The core architecture principle isreuse before duplication, with controlled specialization where business requirements demand it.
Study Guide Reference:Catalog Management — Product Catalog Management; catalog architecture; reusable products, attributes, selling models, and bundles.
===============
