Exam Certified Data Architect topic 1 question 3 discussion

Salesforce has a native price book option, but the customer would need to build a custom price book that has the rules configured via a territory/region picklist. This would need to be done in a custom price book, which is separate from the standard price book. I think as a result, C fits the bill a little bit better. D is clearly out, because there's no need for a custom object when SF natively has price book configurations, and the client specifically wants minimum code change (factor #4). B I think is unnecessary, as SF has native custom price book configurations, so there's no need to create a custom metadata type. A is too generic, as the customer needs the hierarchy of Location/Region, and therefore needs custom price book.

This is honestly a badly worded question, that could lead to a lot of people picking either A or C. Salesforce has a native price book option, but the customer would need to build a custom price book that has the rules configured via a territory/region picklist. This would need to be done in a custom price book, which is separate from the standard price book. I think as a result, C fits the bill a little bit better. D is clearly out, because there's no need for a custom object when SF natively has price book configurations, and the client specifically wants minimum code change (factor #4). B I think is unnecessary, as SF has native custom price book configurations, so there's no need to create a custom metadata type. A is too generic, as the customer needs the hierarchy of Location/Region, and therefore needs custom price book. Reference: https://help.salesforce.com/s/articleView?id=sf.pricebooks_landing_page.htm&type=5

B. Custom Meta datacan be deployed with SFDX from one environment to another. That makes more sense than storing the configuration in custom objects. Include the config in the code is although not a good idea.