New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified B2B Solution Architect (Arch-301) Exam - Topic 9 Question 47 Discussion

Actual exam question for Salesforce's Salesforce Certified B2B Solution Architect (Arch-301) exam
Question #: 47
Topic #: 9
[All Salesforce Certified B2B Solution Architect (Arch-301) Questions]

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?

Show Suggested Answer Hide 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.


Contribute your Thoughts:

0/2000 characters
King
3 months ago
I think option C makes the most sense for long-term stability.
upvoted 0 times
...
Elenore
3 months ago
Including it now could mess up the MVP timeline.
upvoted 0 times
...
Mendy
3 months ago
Wait, can they really fit that in this sprint?
upvoted 0 times
...
Marica
4 months ago
I agree, prioritization is key here!
upvoted 0 times
...
Jules
4 months ago
Sounds like they should just add it to the backlog.
upvoted 0 times
...
Goldie
4 months ago
I recall that MVP should focus on core functionalities, so maybe we shouldn't include this right now. It might complicate things too much.
upvoted 0 times
...
Leota
4 months ago
I think we learned that if the technical effort is low, it might be okay to include it in the current sprint, but I’m not completely sure.
upvoted 0 times
...
Ines
4 months ago
This feels similar to a practice question we had about backlog management. I think adding it to the backlog makes sense, but I’m uncertain about the timing.
upvoted 0 times
...
Glen
5 months ago
I remember discussing how sprint planning should prioritize feasible changes, but I'm not sure if tiered pricing fits in this sprint.
upvoted 0 times
...
Loren
5 months ago
I'm a bit confused on the best approach here. On one hand, it seems like a reasonable request that could be accommodated. But on the other hand, if it requires extending the CPQ B2B Commerce Connector, that could complicate things. I think I'd need to do a bit more research to determine the best way forward.
upvoted 0 times
...
Sabrina
5 months ago
I agree with Whitney. This new requirement sounds like it might need some additional development effort, so it's probably best to add it to the backlog and prioritize it for the next sprint rather than trying to squeeze it in now.
upvoted 0 times
...
Whitney
5 months ago
Hmm, I'm not sure about that. Adding tiered pricing and mapping it to discount schedules could require some more technical work on the CPQ B2B Commerce Connector. I'd lean towards treating it as a new user story and prioritizing it for the next sprint.
upvoted 0 times
...
Florinda
5 months ago
This seems like a pretty straightforward requirement, so I'd recommend including it in the current sprint since the CPQ and B2B Commerce Connector are already set up.
upvoted 0 times
...
Mammie
1 year ago
Hold up, fellas. I'm thinking D is the way to go. Let's get this baby prioritized and groomed first. Don't want any surprises, am I right? *winks*
upvoted 0 times
...
Arlene
1 year ago
C, for sure. Let's not rock the boat too much, you know? Better to leave the heavy lifting for the next sprint. Gotta keep that MVP nice and lean, am I right?
upvoted 0 times
Trinidad
1 year ago
D) Add the request as a new user story to the product backlog, and further schedule a meeting for prioritization and grooming.
upvoted 0 times
...
Melodie
1 year ago
A) Convey that this can be potentially picked up in the next sprint since the technical changes needed for this new user story are low effort.
upvoted 0 times
...
...
Shaquana
1 year ago
I'm with you, this is totally doable. B is the clear choice here. Plus, who doesn't love a bit of tiered pricing? It's like a secret menu for the corporate world.
upvoted 0 times
Alex
1 year ago
Tess: Definitely, it will add a lot of value to our CPQ and B2B Commerce solution.
upvoted 0 times
...
Gary
1 year ago
User 3: Let's make sure to prioritize this in the sprint planning meeting.
upvoted 0 times
...
Tess
1 year ago
User 2: Absolutely, it's like unlocking hidden features for our customers.
upvoted 0 times
...
Germaine
1 year ago
User 1: I agree, B is the way to go. Tiered pricing is a game changer.
upvoted 0 times
...
...
Corrinne
1 year ago
B is the way to go! We've already got the CPQ B2B Commerce Connector set up, so why not just knock this out in the same sprint? Let's get it done, my dude!
upvoted 0 times
Yuette
1 year ago
B) I agree, let's just get it done in the same sprint. It makes sense since we already have everything set up.
upvoted 0 times
...
Rosamond
1 year ago
A) Convey that this can be potentially picked up in the next sprint since the technical changes needed for this new user story are low effort.
upvoted 0 times
...
Tish
1 year ago
B) Include it as a user story and accommodate it in the same sprint, since this is a feasible requirement and the CPQ B2B Commerce Connector is already set up.
upvoted 0 times
...
...
Coleen
1 year ago
I agree with Elly, it's better to address it now rather than delaying it.
upvoted 0 times
...
Elly
1 year ago
I think we should include it in the same sprint since it's feasible.
upvoted 0 times
...

Save Cancel