Yeah, B makes sense here. Product Attributes lets you keep a single product and add skills or roles as attributes during quoting, which controls SKU sprawl. Not 100% sure but pretty confident given how CPQ handles config.
Q: 9
A Global System Integrator (GSI) provides consulting services by offering a variety of roles and skills
based on the needs of the customers. The GSI has a global workforce of 30,000 consultants with
expertise in many different technologies.
Currently, the GSI uses standard Salesforce functionality to quote using Opportunities, Quotes, and
Pricebooks. As its consultants have so many different roles and skills, it maintains a large product
catalog with upward of a million SKUs. A new product is created each time a new skill is added.
How should the GSI use Revenue Cloud to solve its SKU proliferation issue?
Options
Discussion
Option B, C is tempting but Product Attributes (B) directly solve SKU sprawl for variable skills, not just grouping.
B . Product Attributes actually fix SKU sprawl by letting you configure variations (like skills) at quote time, not as separate SKUs. Product Category is more about grouping, which isn't solving the main issue here. Pretty sure on this but open to other takes.
B or maybe A, but I think B is the best fit since Product Attributes let you keep one base product and just change the skills dynamically. A is more for grouping, not reducing SKU count. Open to other views here!
B based on how the official study guide and some hands-on labs cover Product Attributes for managing catalogs with tons of variations. This kind of thing comes up a lot in practice sets too.
B , but if they also needed complex bundling *and* reporting hierarchies for skills, I could see C as a tricky edge case. Still, Product Attributes (B) fixes SKU sprawl directly. Only exception is if they require strict product taxonomy for compliance reports, which isn't mentioned here.
Not A, B. Only Product Attributes directly tackle the SKU sprawl by letting you handle variations without separate SKUs.
A is wrong, B. Product Attributes lets you customize options on the quote instead of adding new SKUs every time, so it addresses the SKU sprawl directly. Pretty sure that's what they're looking for here.
C
B is likely right. I remember seeing similar case studies in the official guide and some practice tests where Product Attributes got rid of endless SKUs by letting you configure details like skills per quote. Anyone got a real project example that showed otherwise?
Be respectful. No spam.
Question 9 of 25