Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam CPQ-301 Topic 11 Question 39 Discussion

Actual exam question for Salesforce's CPQ-301 exam
Question #: 39
Topic #: 11
[All CPQ-301 Questions]

Universal containers has a fixed bundle with selected Product Options, After selecting the bundle, the user should bypass the configuration process.

How should the Admin set up the bundle to meet this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: A, B

Contribute your Thoughts:

Tamar
1 months ago
Universal Containers, more like Universal Headaches. But hey, at least they're not asking us to build a rocket to the moon!
upvoted 0 times
Serina
5 days ago
C) Set the bundle product record filed Configuration type to Allowed and Configuration Event to Always.
upvoted 0 times
...
Colette
9 days ago
A) Set the bundle product record fields Configuration Type to Disabled and Configuration Event to Always.
upvoted 0 times
...
...
Lyla
1 months ago
Ah, the age-old question: to configure or not to configure? That is the bundle dilemma!
upvoted 0 times
...
Dierdre
1 months ago
D sounds like it might let the user accidentally configure the bundle, which goes against the requirement. Better to just disable the whole process.
upvoted 0 times
Adrianna
2 days ago
C) Set the bundle product record filed Configuration type to Allowed and Configuration Event to Always.
upvoted 0 times
...
Jessenia
4 days ago
A sounds like the best option to prevent accidental configuration.
upvoted 0 times
...
Delila
6 days ago
B) Set the bundle product record filed Configuration Type to Required and Configuration Event to Always.
upvoted 0 times
...
Margurite
7 days ago
A) Set the bundle product record fields Configuration Type to Disabled and Configuration Event to Always.
upvoted 0 times
...
...
Lizette
2 months ago
I'm going with C. Allowing the configuration but always showing the bundle should work, right? Though I'm not sure why you'd want to allow configuration for a fixed bundle...
upvoted 0 times
Roslyn
12 days ago
User3: I'm not sure why you would want to allow configuration for a fixed bundle, but C could work too.
upvoted 0 times
...
Alex
19 days ago
User2: I agree with User1. Option A seems to be the best choice for this scenario.
upvoted 0 times
...
Ashlee
20 days ago
User1: I think A is the correct option. Disabling configuration for the bundle makes sense.
upvoted 0 times
...
...
Haydee
2 months ago
B is a bit confusing. If it's a fixed bundle, why would you set Configuration Type to Required? That doesn't make sense.
upvoted 0 times
Anthony
1 months ago
C) Set the bundle product record filed Configuration type to Allowed and Configuration Event to Always.
upvoted 0 times
...
Staci
1 months ago
A) Set the bundle product record fields Configuration Type to Disabled and Configuration Event to Always.
upvoted 0 times
...
...
Clay
2 months ago
I'm not sure, but I think option A is the best choice based on the requirement.
upvoted 0 times
...
Rosamond
2 months ago
Option A seems straightforward and meets the requirement. Disable the configuration process and always show the bundle.
upvoted 0 times
Isaiah
1 months ago
No, that would force users to go through configuration.
upvoted 0 times
...
Truman
2 months ago
B) Set the bundle product record filed Configuration Type to Required and Configuration Event to Always.
upvoted 0 times
...
Deeanna
2 months ago
That sounds like the right choice.
upvoted 0 times
...
Trina
2 months ago
A) Set the bundle product record fields Configuration Type to Disabled and Configuration Event to Always.
upvoted 0 times
...
...
Cordelia
2 months ago
I agree with Lucina, that option makes sense because it will bypass the configuration process.
upvoted 0 times
...
Lucina
3 months ago
I think the Admin should set the bundle product record fields Configuration Type to Disabled and Configuration Event to Always.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77