You are implementing the Design Document for a large Enterprise Revenue Cloudprojecthaving multiple lookup price rules supporting a complex pricing requirement in the Buildphase. During construction the customer discovers additional logic and external datastores that need to be incorporated in order to achieve the correct pricing in a particular setof use cases. You estimate the lookup price rules will need to be modified, additional ruleswill need to be created and API development will beneeded. As an Implementationconsultant what is the appropriate course of action that should take in this predicament?
Had something like this in a mock, and C fits best. When new requirements come up in the build phase that need API work or more rules, that's clearly a scope change so it has to go through PM for impact analysis (scope, time, cost). If you just implement straight away it breaks good governance. Pretty sure it's C but happy to hear other takes.
I don't think it's D. C is the right move here because when scope and budget may be affected, the PM has to evaluate the impact before anyone implements. D seems logical but skips that governance step. Pretty sure this is what Salesforce expects for enterprise projects, but open to counterpoints if I've missed something subtle.
Yeah, it's gotta be C. Any time scope, timeline or budget might change, you loop in the PM to handle impact assessment and next steps. Jumping straight into technical changes without proper approval is risky, even if the architect agrees. Pretty sure that's Salesforce best practice but let me know if I'm missing something.