MENU
A company wants to charge differentprices for a service depending on the bandwidth and network selected by the customer.
* If bandwidth is 1 GB and network is ''Internet the price is $10/monthly and $5/one-time-charge
* If bandwidth is 10 GB and network is ''external,'' the price is $20/monthly and $0/one-time-charge
Which type of pricing should the developer configure to meet these requirements?
Suggested Answer: D
Get Premium Salesforce Certified Industries CPQ Developer (Ind-Dev-201) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
HU
Huey
10 months ago
I agree, $10 for 1 GB is a steal!
MO
Moon
10 months ago
Wait, can they really charge like that? Seems a bit odd.
EI
Eileen
10 months ago
Definitely attribute-based pricing! Makes sense with the different options.
WI
Wilda
10 months ago
I think context rules could work too, but not sure.
CO
Cordelia
11 months ago
Sounds like attribute-based pricing fits best here.
AM
Amos
12 months ago
I’m leaning towards Usage Pricing, but I’m not confident. The one-time charge aspect is throwing me off a bit.
AL
Altha
12 months ago
I feel like Context rules for pricing adjustments could apply here since the prices change based on specific conditions like bandwidth and network type.
TW
Twila
1 year ago
This seems similar to a practice question we did on tiered pricing models. I think it might be Attribute Based Pricing, but I could be wrong.
JA
Janessa
1 year ago
I remember we discussed different pricing strategies, but I'm not entirely sure which one fits this scenario best.
CO
Corrie
1 year ago
This seems straightforward to me. The company is offering different prices based on the customer's choices, so it's clearly a case of context rules for pricing adjustments. I'm going with option B.
RE
Rebecka
1 year ago
Okay, I think I've got it. The pricing is based on the specific attributes of bandwidth and network, so option D, Attribute Based Pricing, is the correct answer. The key is that the price changes depending on the customer's selections.
TO
Tonja
1 year ago
Hmm, I'm a bit confused. The question mentions different prices for different bandwidth and network combinations, but it's not clear to me how that maps to the pricing options given. I'll need to think this through carefully.
CA
Casandra
1 year ago
This looks like a classic case of attribute-based pricing. The pricing is determined by the bandwidth and network selected, so I think option D is the way to go.
KA
Kasandra
1 year ago
I see your point, Sharan, but I still think Attribute Based Pricing is the best option for this situation.
CO
Cora
1 year ago
Context rules for pricing adjustments? Sounds like a fancy way of saying 'charge whatever you want.' Attribute Based Pricing is the clear winner here.
KR
Krystal
11 months ago
Definitely leaning towards Attribute Based Pricing too!
SA
Salome
11 months ago
I agree, Attribute Based Pricing makes the most sense.
RA
Rachael
11 months ago
Usage Pricing could work, but it’s not as clear-cut.
BO
Boris
11 months ago
Context rules seem too vague for this.
FL
Florinda
1 year ago
Usage Pricing? Nah, this is all about the specific features of the service. Attribute Based Pricing is the only option that makes sense.
LE
Leonida
1 year ago
Yeah, I agree. It allows for different prices based on specific attributes like bandwidth and network.
RI
Ricki
1 year ago
I think Attribute Based Pricing is the way to go here.
SH
Sharan
1 year ago
I believe Context rules for pricing adjustments could also work well here.
BR
Brynn
1 year ago
Ha! Cost and Margin Pricing? That's like trying to charge the same for a Ferrari as a bicycle. Attribute Based Pricing is the way to go.
TE
Teresita
1 year ago
User 1: I think Attribute Based Pricing is the best option here.
AH
Ahmed
1 year ago
Definitely gotta go with Attribute Based Pricing here. The different prices are based on the attributes of the service, like bandwidth and network type.
LO
Lonna
1 year ago
I agree with Melodie, Attribute Based Pricing makes sense for this scenario.
ME
Melodie
1 year ago
I think the developer should configure Attribute Based Pricing.