Salesforce ARC-801 Exam - Topic 2 Question 56 Discussion

Actual exam question for Salesforce's ARC-801 exam

Question #: 56
Topic #: 2

Universal Containers is in the process of implementing a CPQ and B2B Commerce solution. The Technology team hascompleted the development for the current sprint and is demonstrating the functionalities to the business stakeholders during their sprint demo. While demonstrating products and pricing, and Sync between B2B and CPQ when requesting a quote, the stakeholders make a new request to include tiered pricing and map it to discount schedules on CPQ.

Which approach should a Solution Architect recommend while addressing the feedback from the stakeholders?

AConvey that this can be potentially picked up in the next sprint since the technical changes needed for this new user story are low effort.

BInclude it as a user story and accommodate it m the same sprint, since this is a feasible requirement and the CPQ B2B Commerce Connector is already set up.

CConvey that it is not recommended to include M the initial MVP, since an extension is needed on the CPQ B2B Commerce Connector for the new requirement.

DAdd the request as a new user story to the product backlog, and further schedule a meeting for prioritization andgrooming.

Show Suggested Answer

Suggested Answer: D

CPQ B2B Commerce Connector is a tool that synchronizes data from CPQ product and pricing objects to B2B Commerce objects1.

CPQ uses discount schedules and B2B Commerce uses tiered pricing to handle volume-based pricing23.

The connector does not support mapping tiered pricing to discount schedules out of the box23.

The connector uses pricing from B2B Commerce to define the pricing on the generated quote lines by setting their Special Price fields4.

Incorporating new requirements, such as tiered pricing and mapping to discount schedules in CPQ, into an ongoing Salesforce CPQ and B2B Commerce project requires careful consideration of project scope, timelines, and resource availability. Adding the new requirement as a user story to the product backlog allows for a structured approach to evaluating its impact on the project. Scheduling a subsequent meeting for prioritization and grooming ensures that stakeholders can discuss the new requirement in detail, assess its feasibility, and decide on its inclusion in the project timeline. This approach aligns with agile project management best practices, allowing for flexibility in responding to new requirements while maintaining project focus and efficiency.

by Joni at Nov 19, 2025, 06:43 PM

Limited Time Offer

25%

Off

Get Premium ARC-801 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Aliza

24 hours ago

Sounds like they should just add it to the backlog.

upvoted 0 times

...

Scarlet

6 days ago

Option D is too slow. The team should be able to handle this new requirement within the current sprint.

upvoted 0 times

...

Anjelica

11 days ago

Haha, the stakeholders are really keeping the team on their toes with these new requests! Option B is the way to go.

upvoted 0 times

...

Teri

16 days ago

Option C is not a good idea. Delaying the implementation of this feature until the next sprint could disappoint the stakeholders and impact the project timeline.

upvoted 0 times

...

Nickole

22 days ago

I agree with Option B. Accommodating the new requirement in the same sprint is the most efficient way to address the stakeholders' feedback.

upvoted 0 times

...

Merilyn

27 days ago

Option B seems like the best approach. The requirement is feasible and the connector is already set up, so it should be doable within the current sprint.

upvoted 0 times

...

Shannan

1 month ago

I feel like including it in the same sprint, as in option B, could lead to rushed work. It might be better to add it to the backlog instead.

upvoted 0 times

...

Tanesha

1 month ago

I think we practiced a similar question where we had to prioritize new features. Option C makes sense if it’s not part of the MVP.

upvoted 0 times

...

Nilsa

1 month ago

I’m not sure if the effort for tiered pricing is really low, like option A suggests. It seems like it could be more complex than that.

upvoted 0 times

...

Lashawn

2 months ago

I think option B is the best approach here. The connector is already set up, so it seems like a good opportunity to address the stakeholder's request and deliver value in the current sprint.

upvoted 0 times

...

Beatriz

2 months ago

Option A sounds tempting, but I'm not sure the stakeholders will be happy with pushing this to the next sprint. If it's a feasible requirement, we should try to include it now.

upvoted 0 times

...

Dominque

2 months ago

Hmm, I'm leaning towards option D. Adding it to the backlog and prioritizing it later seems like the most prudent approach. We don't want to overcommit the team in the current sprint.

upvoted 0 times

...

Dong

3 months ago

I remember we discussed how adding new user stories mid-sprint can disrupt the team's focus, so I’m leaning towards option D.

upvoted 0 times

...

Kenny

3 months ago

I'm a bit confused on this one. The question mentions that technical changes are needed, so I'm not sure if it's really that low effort. Maybe option C is the safer bet to avoid scope creep?

upvoted 0 times

...

Michal

3 months ago

I think option B is the way to go here. The CPQ B2B Commerce Connector is already set up, so it seems like a feasible requirement that can be accommodated in the current sprint.

upvoted 0 times